AltME groups: search
Help · search scripts · search articles · search mailing listresults summary
world | hits |
r4wp | 4 |
r3wp | 80 |
total: | 84 |
results window for this page: [start: 1 end: 84]
world-name: r4wp
Group: #Red ... Red language group [web-public] | ||
Kaj: 4-Jun-2012 | Red is actually quite suitable for CGI, because the compiled executables are absolutely tiny, like they were in languages such as C when CGI was introduced. This means the performance will be quite good, not like the performance hit CGI suffers with heavy modern programming environments such as REBOL where the whole virtual machine needs to be started for every request. At the same time, you still have the advantages that made CGI popular: simplicity, robustness and security | |
Group: Rebol School ... REBOL School [web-public] | ||
Arnold: 7-Sep-2012 | Thank you, this works! I found and old conversation on ALTME this afternoon but that could not convince me being the answer, this answer will replace the old one. (I even typed get_env the first time). And for completeness I will write how to use it (cut and paste code) requestedurl: get-env "REQUEST_URI" | |
Cyphre: 7-May-2013 | It's even in the lates public source release here: http://development.saphirion.com/downloads/ so if anyone have time to make pull-request? | |
Group: #Red Docs ... How should Red be documented [web-public] | ||
Gregg: 4-Dec-2012 | I'm trying the github Windows client, which should sync, but only have my fork in it right now. I thought the target workflow (in general) was to fork, push to that, then submit a pull request. My problem is spending little time on it, then letting it sit idle while it leaks out of my brain. |
world-name: r3wp
Group: !AltME ... Discussion about AltME [web-public] | ||
Brock: 19-Jan-2005 | Feature Request: I'd like a one button push or automtated/timed solution to bring up the "Getting Started Window" OR remove focus from all groups. Why? If you aren't actually using AltME (it's running in the background), and you get new messages, the messages in the group you are currently 'in' aren't highlighted as new. Which can make it confusing when the tool tells you a new message has been received, but you don't see a hightlight on any group (and don't check the time on the messages in the 'current' group). | |
Brock: 1-Jun-2006 | My second feedback/request was asking to only have to type in user credentials once per AltMe session. I don't auto-populate my userid and password as this computer is a multi-user computer that doesn't take advantage of the built-in OS multi-user features (setup as single user). So, switching between Worlds requires me to login each time I visit worlds I was already logged into. | |
Ingo: 26-Jan-2007 | I'll third the second request, (which is now the "0"th) ... Don't loose any data!!! and related subrequests ... - don't drop me out of whatever I'm reading / writing, just because altme lost connection ... who cares? But I DO care, if suddenly the unread markings are lost - If I start typing a message in one channel, then go to a second, clear the input field, and remember the message for the channel I started typing it, so that I can send it later, when I go back to that channel - if I write a message, but don't have a connection, save it, and ask me whether I stil want to send, when the connection comes back (with a time threshold, send silently 5 minutes later, but not 5 days) ( Yes, this is debatable, what if I realize, that I _wanted_ to send this to a different channel? | |
Ingo: 31-Jan-2007 | OK, it's time again for the twice weekly drive Reichart crazy competition to get your favourite bugs fixed ... ;-) I'll just copy verbatim from one of my last entries ... I'll third the second request, (which is now the "0"th) ... Don't loose any data!!! and related subrequests ... - don't drop me out of whatever I'm reading / writing, just because altme lost connection ... who cares? But I DO care, if suddenly the unread markings are lost - If I start typing a message in one channel, then go to a second, clear the input field, and remember the message for the channel I started typing it, so that I can send it later, when I go back to that channel - if I write a message, but don't have a connection, save it, and ask me whether I stil want to send, when the connection comes back (with a time threshold, send silently 5 minutes later, but not 5 days) ( Yes, this is debatable, what if I realize, that I _wanted_ to send this to a different channel? Not yet teamwork, but I _can_ be persistant ;-) | |
Brock: 14-Nov-2008 | AltME feature request. Include the date/time as a second column a group was last updated. Since we don't have the ability to synch what was read between each instance of AltME that we read, having the last date/time listed we could quickly select through the groups we have already visited in a previous session on another machine. Although synching what was last accessed would be the ultimate fix. :-) | |
Gerard: 12-Jul-2011 | @ Reichart : We were discussing in the OPEN GL group about the default way AltMe permits to enter text - and we were 3 that think the default way to enter text would be the EDIT mode (the one that accepts Line feeds without submitting the post automatically. Would you be considering this option in a future release - even if I now realize that this is a global switch since when I submits new posts this mode is kept alive. I didn't ask for others to vote for this change but you can do it if you want - I find it really annopying - more than the obligation to commit messages by having to use the mouse each time. I know it's a productivity consideration but as I can't reedit my sent posts, sometimes they didn't look good - until I asked someone how to enter LFs. Thanks a lot for considering this request. Regards, Gerard | |
Group: Core ... Discuss core issues [web-public] | ||
MichaelB: 3-Feb-2006 | this might be something dangerous: write %test.r "hello" path: what-dir remove back tail path write %test.r "hello" ; this fails problem is: what-dir returns directly system/script/path what seams to be used in order to resolve relative file values I just recognized it using the request-dir from didec which was in the rebgui distro -038 (he's doing this in the request-dir function in the line with if all [not empty? path slash = last path][remove back tail path] so question is whether this is a bug and belongs to rambo, is ok (I don't think so) or what else ? might also be that didec changed this in a later version (script was dated 2003 and maybe at this time 'what-dir had a different behavior), but this doesn't matter regarding what 'what-dir returns | |
yeksoon: 2-Mar-2006 | thanks for the one-liner solution.. but I would also like to request for additional refinements to be added to 'NOW'... it just seems more natural to me if we can use refinements for the time as well | |
RobertS: 1-Apr-2008 | Diss'ing IDE's might alienate some Smalltalk folk. I cannot imagine maintaining an application suite such as I deal with everyday without an IDE. I just wish it was not eclipse ... Of course only wimps used a Disk Operating System and real men code in machine codes only ... and real pro's dictated their SNOBOL punch cards to lovely assistants ... and ANT scripts are for sissies. Some must have ridiculed Tcl, Expect and TK in their day ... but if my IDE can facilitate my efforts to systematically (key word there) shrirnk company''s codebase as it becomes more reliable with better test coverage then maybe a refactoring browser would be a good tool after all. Even better if it is an integrated part of the IDE, as in Dolphin Smalltalk or Squeak Smalltalk or Smalltalk/X or Cincom Visual Smalltalk. Not that I couldn't survive on grep and diff's. But once the codebase is too large for any one person to author or maintain on their lonesome, a tool that remebers what you did last and where can be a god-send. If you want to know hell without an IDE join an actuarial department working in APL. There you don't even know if they have talent: you just hope most of it works as each quarter rolls around and try to survive year-end. But you know they're smart, cuz after all, they're actuaries - and look at all that APL code in all those files ... of course a few of them look back wistfully at their student days in C with Borland's decent IDE. REBOL [ File: %vid-usage.r Date: 09-Jan-2004 Title: "VID Usage" Purpose: "VID Usage Tutorial with Runnable Examples" Version: 1.2.1 Author: "Cybarite" Edits: RobertS Source: { Based on %easy-vid.r by Carl Sassenrath. Clips from various sites including email that are attributed in the section } library: [ level: 'intermediate platform: 'all type: [tutorial] domain: [gui] tested-under: [view 1.2.8.3.1 on W2K] support: none license: none see-also: none ] ] flash "Fetching image..." read-thru/to http://www.rebol.com/view/demos/palms.jpg%palms.jpg read-thru/to http://www.rebol.com/graphics/reb-logo.gif%rebo-logo.gif read-thru/to http://www.rebol.com/view/bay.jpg%bay.jpg pic: %palms.jpg unview customer: make object! [ ; this sets a default customer object in case the user does not push the samples in order name: "Rosetta Stone" date-of-birth: 14-March-1959 ] stylize/master [text-note: txt maroon bold] ; this sets a default for users who run the samples out of order ; polished is an image that is embedded in this script file ; so that no outside files need to be loaded. ; This technique is used in many of the REBOL samples polished: load #{ 89504E470D0A1A0A0000000D49484452000000670000003808020000006FFB71 8C0000001374455874536F667477617265005245424F4C2F566965778FD91678 0000039B49444154789CCD9BD14E2B310C44F3FFFF521E2AC1C395E00589EF02 5DD8D226713C339EECBD928510A4893D3EF67AB76D7B7E79FEB2D73FAFBDBD1D 36FEEBAF7DBF70FEDABABD0D56F0E1B6E0B6FED7AE81050B2E4F97AF9FED6185 45022048CA2C6920361F1336580B35A63C4E4F12808D378124CE9C81880B186C 14175A1DE9C0C2A2E785B6B64CA62EF6C626330250A932064CB984F3358FA77F BC7F8CD657685E5FB03415A34B9E3226C1484A1ACA6DB6974597699EFB6C2F4E C44B92E17454A309F14F348DDD4D5B98195BB2AF6B7E4E545B57FEBAE0415DA0 43EFE62C70B196362285D74C35F0782ECF26A0FC8492E20EAAED6CC35ACE13FC 61646467C69D5715EA4F9D3725B1703BF45AB2768A9D5F59CA6E716E5A747CBF 23D6A7E418C2C53C6EB440FCE803B106E6D94C8AAF4B42694871B9FB237035C8 70E5A0200D4A7E4553E952A6F435BA247DD4B83A5DB18D26AA4D5E39E0CA4107 7B0F86C7F19EC685B5EFE57D28E02E411CC2238C0304B5065D26DCC1DA9A02FC CE4EBD19A0C58D9BE039179086B6DB20519A1F5C8194071DBB115703B996FF37 4BE0F5AA269B18CFC9C6CC1FC3D5A0D6B62C6AEA112236F38195B88DF12F9C9B B45B1C6C637B161E1D5BCF6D8807A0437366CB21D90462F2BD3E827C96CB0483 D67B99916407E99E69FD12F46A50C973856268A5DC345259837D8827E00FF890 452D0B5D0D38932F3C65B9614B4F720901B96565DCCBD7236B7C66B650868D08 9BFA26EBB36DCAA5E3B120339E5EBE3B468E6B68FB3041E79229047367ADDC14 F7B376F26B2722024A41998813A04CB91A475C11C9054536473CA3F7365C0D30 9E65A0BA6D5977CFEE030BD626B9E2E5DFE76E51AFF9CADA6308F899C76E756A 03D4796E80532E986D273B71CEA8D81672739E0F1B329F8E999D0D9D04080769 CABC1D21260C2BB8E43D2A9D70BE3A2207D66EA09E5BCAFFB742F9F0A0C37677 222CFE9B7C2865192B3FAC5988E0385747334BD8288041E0DFBF4F2AD44804B4 6DADAF2BE98C5D02458059B3571CA91481B09580A9D6E827B184DD3756D6BF7E 7376F81ED59E46633384296A9A4BA7D4E3B8CBD3E566F1948B754731E0EBC41B 246774BD7BBBCA612D8CA7CC85A7C1ED093B75721DCED1D7E279871668830AE7 B782F5E9FDE4918360C9F666A6F61647F2EDB342A2FA3F6E9B0C8AC2699B9B3F 53847BB992B5707FDE5B6D721EA3EB55E3D8190D8BD998923A68917BE3FEDD32 EE1BDCA216275C1CCFBD0A07F35A40A6CC05A1357E6BF512D26DC470BAC927A3 B0078A42DD22E10000000049454E44AE426082 } content: {VID Usage - REBOL Visual Interfaces ===Updates --01-Apr-2008 * Fixed oddity with last item on stylesheets which was locking up some versions of VIEW ---09-Jan-2004 * Fixed slider initialize. * Focus section was not parsed out. --- fixed * Fixed some text errors for the parsing of === ---07-Jan-2004 * Revived vid-usage.r * added more examples from the script library * manage source as vid-usage.leo an outliner file ---12-August-2001 Added supply examples. See: !List/Supply !List With Supplied Data !Supply List With Scroll ---13-August-2001 !Add Subpanel example ported by Anton ===Caveats ---Work In Progress This is a work in progress. Whether the progress will continue depends on the feedback. ---All Rights Reserved The work is based on the documentation of REBOL View provided by REBOL Technology and its mailing list. All rights to this documentation remain the property of REBOL Technology. ---Plagiarized Examples Things are shamelessly plagiarized. There are many experts on the mailing list whose work is included here; most notably the examples from the REBOL documentation. ---Approach The approach that this document uses is to use REBOL/View/VID to demonstrate its abilities and give a visual tutorial. To enable this some changes have been made to the core %easyvid.r program from Carl Sassenrath. A scoll bar was added to the right pane because it was just too difficult to constrain the examples to the screen real estate that was available. ---Order Order The order of the items needs some work. The easyvid presentation approach today does not allow for the drilling down and expansion of an outline tree which is needed for a large amount of documentation. The preferred approach is to put a multi-level tree for navigation purposes and then allow navigation up and down the tree. ===To Do * make this a true outline tree * re-organize it better * update as requested and as possible by suggestions on AltME's REBOL world under group EasyVID * correct numerous flaws * better scrolling implementation using the updates that have been used in other examples such as Didier's %delete-email.r * allow clipping to clipboard like AltME does on a row for the source examples ===Introduction to VID With REBOL/View it's easy and quick to create your own user interfaces. The purpose of this tutorial is to teach you the basic concepts or REBOL/View interfaces in about 20 minutes. VID is REBOL's Visual Interface Dialect. A dialect is an extension of the REBOL language that makes it easier to express or describe information, actions, or interfaces. VID is a dialect that provides a powerful method of describing user interfaces. VID is simple to learn and provides a smooth learning curve from basic user interfaces to sophisticated distributed computing applications. ---Creating VID Interfaces VID interfaces are written in plain text. You can use any text editor to create and edit your VID script. Save your script as a text file, and run it with REBOL/View. !Note: Using a word processor like Word or Wordpad is not recommended because files are not normally saved as text. If you use a word processor, be sure to save the output file as text, not as a document (.doc) file. Recommendation: Look at TextPad from http://www.textpad.com ===Minimal VID Example Here is a minimal VID example. It creates a window that displays a short text message. Only one line of code is required: view layout [text "Hello REBOL World!"] You can type this line at the REBOL console prompt, or save it in a text file and run it with REBOL. If you save it as a file, the script will also need a REBOL header. The header tells REBOL that the file contains a script. Here is an example of the script file with a header: REBOL [Title: "Example VID Script"] view layout [text "VID Example!"] You can also add buttons and other gadgets to the script. The example below displays a text, list of files, and a button: view layout [ h2 "File List:" text-list data read %. button "Great!" ] !Click on the examples above to see how they will appear on your screen. Click on their close box to remove them. All of the examples that follow can be viewed this way. ===Window Management The code that displays the examples also shows how to manage the number of windows that are open. Look at the show-example block in the code near the end of this script. The location of the example window is also managed here by keeping track of the co-ordinates for the sample. After the sample window is moved, the next use will open at the same location. ===Pre-loaded Images For this script, the image which represented a Portable Network Graphic definition of an image is held in the script and loaded. For a small number of graphics, this can achieve some packaging and performance benefits. The image "polished" is used through the script to achieve the polished steel look that is one the outer frame. backtile polished orange button 200x50 "Polished Steel Look" polished ===Two Basic Functions Two functions are used to create graphical user interfaces in REBOL: VIEW and LAYOUT. The LAYOUT function creates a set of graphical objects. These objects are called faces. You describe faces with words and values that are put into a block and passed to the LAYOUT function. The VIEW function displays faces that were previously created by LAYOUT. The example below shows how the result of the LAYOUT function is passed to the VIEW function, and the interface is displayed. view layout [ text "Layout passes its result to View for display." button "Ok" ] Click on the above example to view it. !Note: the block provided to a layout is not normal REBOL code, it is a dialect of REBOL. Using a dialect makes it much easier to express user interfaces. ===Styles Styles describe faces. The examples above use the text and button styles to specify a text line and a button. REBOL has 40 predefined face styles. You can also create your own custom styles. Here are a few example styles: view layout [ h1 "Style Examples" box brick 240x2 vtext bold "There are 40 styles built into REBOL." button "Great" toggle "Press" "Down" rotary "Click" "Several" "Times" choice "Choose" "Multiple" "Items" text-list 120x80 "this is" "a list" "of text" across check radio radio led arrow below field "Text Entry" ] The words like backdrop, banner, box, text, and button are styles. ===Facets Facets let you modify a style. For instance, you can change the color, size, text, font, image, edge, background, special effects, and many other facets of a style. Facets follow the style name. Here is an example that shows how you modify the text style to be bold and navy blue: view layout [txt bold navy "Facets are easy to use."] The words bold and navy are not styles. They are facets that modify a style. Facets can appear in any order so you don't have to remember which goes first. For example, the line above could be written as: view layout [txt "Facets are easy to use." navy bold] Many facets that can be specified. Here is an example that creates bold red text centered in a black box. view layout [txt 300 bold red black center "Red Text"] You can create facets that produce special effects, such as a gradient colored backdrop behind the text: view layout [ vtext bold "Wild Thing" effect [gradient 200.0.0 0.0.200] ] ===Custom Styles Custom styles are shortcuts that save time. When you define a custom style, the facets you need go into the new style. This reduces what you need to specify each time you use the style, and it allows you to modify the look of your interface by changing the style definitions. For example, here is a layout that defines a style for red buttons. The style word defines the new style, followed by the old style name and its facets. view layout [ style red-btn button red text "Testing red button style:" red-btn "Test" red-btn "Red" ] So, if you wanted to create a text style for big, bold, underlined, yellow, typewriter text: view layout [ style yell tt 220 bold underline yellow font-size 16 yell "Hello" yell "This is big old text." yell "Goodbye" ] ===Master Stylesheet REBOL holds its styles in a master stylesheet. When you are sure that you want to share them without having to add the style sheet line then do it as follows: First add the style to the master sheet: button 200x50 "Define text-note as maroon bold text" [stylize/master [ text-note: txt maroon bold ]] button 200x50 "Define text-note as white italic text" [stylize/master [ text-note: txt white italic ]] Then invoke it: view layout [ across size 200x200 return text-note "This shows a master stylesheet style in use." return text-note "This shows another usage of the same style." return text-note "If you want to see the other style displayed, click the Add Style section again and then use the other button" ] ===Note About Examples !From this point forward, all examples will assume that the view and layout functions are provided. Only the layout block contents will be shown. To use these examples in your scripts, you will need to put them in a layout block, as was shown earlier. For example, code that is written as: view layout [button red "Test it"] will now appear as: button red "Test it" ===Face Sizes The size of a face depends on its style. Most styles, such as buttons, toggles, boxes, checks, text-lists, and fields, have a convenient default size. Here are some examples. button "Button" toggle "Toggle" box blue field text-list If no size is given, text will automatically compute its size, and images will use whatever their source size is: text "Short text line" text "This is a much longer line of text than that above." image %palms.jpg You can change the size of any face by providing a size facet. The size can be an integer or a pair. An integer specifies the width of the face. A pair specifies both width and height. Images will be stretched to fit the size. button 200 "Big Button" button 200x100 "Huge Button" image %palms.jpg 50x50 image %palms.jpg 150x50 ===Color Facets Most styles have a default color. For example the body of buttons will default to a teal color. To modify the color of a face, provide a color facet: button blue "Blue Button" h2 red "Red Heading" image %palms.jpg orange Colors can also be specifed as tuples. Each tuple contains three numbers: the red, green, and blue components of the color. Each component can range from 0 to 255. For example: button 200.0.200 "Red + Blue = Magenta" 200 image %palms.jpg 0.200.200 "Green + Blue" Some face styles also allow more than one color. The effect of the color depends on the style. For text styles the first color will be used for the text and the second color for the background of the text: txt "Yellow on red background" yellow red banner "White on Navy Blue" white navy For other styles, the body of the face is the first color, and the second color will be used as its alternate. button "Multicolor" olive red toggle "Multicolor" blue orange ===Layout Commands To drop user interface elements on the canvas according to VIDs directional layout controls ---Across You are placing elements in a row orientation across return button "A" button "B" button "C" return button "D" button "E" button "F" ---Below You are placing elements in a column orientation below return button "A" button "B" button "C" return button "D" button "E" button "F" ---Mix You can mix the directional controls across return button "A" button "B" below button "C" across button "D" button "E" button "F" ---Padding The pad keyword creates extra padding between styles. It uses a pair or integer value. When it is an integer, spacing is created either horizontally (across) or vertically (below). When it is a pair, the spacing will be created both horizontal and vertically. The following example illustrates both uses. First, the buttons "one" and "two" are padded with an integer representing 40 pixels in one direction. Then the buttons "three" and "four" are padded with a pair representing 40x40 pixels. across button "one" pad 40 button "two" return button "three" pad 40x40 button "four" Padding can be negative. backtile polished orange pad 200x200 button "A" pad -100x-100 button "B" ---Guide A guide is a virtual alignment control title "Buttons Without A Guide" button "one" button "two" return button "three" button "four" return button" five" button "six" With an implicit guide location title "Buttons With An Implicit Guide Location" guide button "one" button "two" return button "three" button "four" return button" five" button "six" With an explicit guide location across title "Buttons With An Explicit Guide Location" guide 55x100 button "one" button "two" return button "three" button "four" return button" five" button "six" ===Tabstops Tabs can be used for alignment. ---Across tabs 200 ; sets tabs every 200 pixels across button 20 "A" tab button 20 "B" tab button 20 "C" tabs 100 ; sets tabs every 100 pixels return button 20 "D" tab button 20 "E" tab button 20 "F" ---Below tabs 200 ; sets tabs every 200 pixels below button 20 "A" tab button 20 "B" tab button 20 "C" tabs 100 ; sets tabs every 100 pixels return button 20 "D" tab button 20 "E" tab button 20 "F" ---Explicit Settings Tabstops can be set at explicit values tabs [100 124 166 212 300] across tab button 20 "A" tab button 20 "B" tab button 20 "C" tab button 20 "D" ===Color Facets Most styles have a default color. For example the body of buttons will default to a teal color. To modify the color of a face, provide a color facet: button 200 blue "Blue Button" h2 red "Red Heading" image polished orange Colors can also be specifed as tuples. Each tuple contains three numbers: the red, green, and blue components of the color. Each component can range from 0 to 255. For example: button 200.0.200 "Red + Blue = Magenta" 200 image polished 0.200.200 "Green + Blue" Some face styles also allow more than one color. The effect of the color depends on the style. For text styles the first color will be used for the text and the second color for the background of the text: txt "Yellow on red background" yellow red title "White on Navy Blue" white navy For other styles, the body of the face is the first color, and the second color will be used as its alternate. button 200 "Multicolor" olive red toggle 200 "Multicolor" blue orange From the mailing list, there was a problem reported in changing button color: view layout [ b: button "New color" [ b/color: random 255.255.255 show b ] ] And the answer was that the gradient of the color was preventing this change from working: style color-changing-button button 0.0.0 ; new style overwrites gradient effect b: color-changing-button "New color" [ b/color: random 255.255.255 show b ] ===Text Facets Most faces will accept text to be displayed. Even graphical faces can display text. For example, the box and image faces will display text if it is provided: box blue "Box Face" image polished "Image Face" Most button faces will accept more than one text string. The strings will be shown as alternates as the face is selected. button 200 "Up" "Down" toggle 200 "Off" "On" rotary 200 "Red" "Green" "Blue" "Yellow" choice 200 "Monday" "Tuesday" "Wednesday" "Thursday" "Friday" text-list 200 "Monday" "Tuesday" "Wednesday" "Thursday" "Friday" When other datatypes need to be displayed as text, use the form function to convert them first: button 250 form now field form first read %. ===Normal Text Style Normal text is light on dark and can include a number of facets to set the font, style, color, shadow, spacing, tabbing, and other attributes. text "Normal" text "Bold" bold text "Italic" italic text "Underline" underline text "Bold italic underline" bold italic underline text "Big" font-size 32 text "Serif style text" font-name font-serif text "Spaced text" font [space: 5x0] Text also includes these predefined styles: title "Title" 200 vh1 "vh1" vh2 "vh2" vh3 "vh3" vh4 "vh4" label "Label" ===Document Text Style Document text is dark on light and can also include a number of facets to set the font, style, color, shadow, spacing, tabbing, and other attributes. txt "Normal" txt "Bold" bold txt "Italic" italic txt "Underline" underline txt "Bold italic underline" bold italic underline txt "Big" font-size 32 txt "Serif style text" font-name font-serif txt "Spaced text" font [space: 5x0] Document text also includes these predefined styles: title "Centered title" 200 h1 "Heading 1" h2 "Heading 2" h3 "Heading 3" h4 "Heading 4" tt "Typewriter text" ===Text Entry Fields Text input fields accept text until the enter or tab key is pressed. A text input field can be created with: field To make the field larger or smaller, provide a width: field 30 field 300 Fields will scroll when necessary. Larger amounts of text can be entered in an area. Areas also accept an enter key and will break lines. area You can also specify the area size: area 160x200 To force the text in an area to wrap rather than scroll horizontally, provide the wrap option: area wrap ===Text Setting To set the value of a text field under program control, use /text: e.g. across backtile polished return t1: txt 200 "This is some original text" return f1: field 200 "Some field text" return a1: area {Some original area text.} wrap 200x80 return button 200 "Change Text" [ t1/text: "Some different text" f1/text: "Some new field text" a1/text: {Some wrapping text in the^/ area field to^/ show that this^/ is supported} show [t1 f1 a1] ] ===Text Lists Text lists are easy to create. Here is an example. text-list "Eureka" "Ukiah" "Mendocino" You can also provide it as a block: text-list data ["Eureka" "Ukiah" "Mendocino"] Almost any type of block can be provided. Here is a list of all the files in your current directory: text-list data read %. Here is a list of all the words REBOL has scanned: text-list data first system/words ===Scrolling Text List A style to allow maintenance of lists from Brett Handley on the REBOL list: style updatable-text-list text-list with [ update-slider: does [ sld/redrag lc / max 1 length? head lines ] ] tl: updatable-text-list 300x100 data copy system/locale/months button 300x20 "Delete first entry on the list" [ remove tl/data tl/update-slider show tl ] button 300x20 "Append the 'now' timestamp to list" [ append tl/data mold now tl/update-slider show tl ] ===Text List Picked Values list-of-letters: text-list "a" "b" "c" "d" "e" button 200 "Pick Item 3" [ clear list-of-letters/picked append list-of-letters/picked pick list-of-letters/data 3 show list-of-letters ] ===Images By default an image will be scaled to fit within a face. image 60x60 polished image polished red Images can be framed in a number of ways: image 100x100 polished frame blue 5x5 image 100x100 polished bevel image 100x100 polished ibevel 6x6 Most other faces can accept an image as well as text: box 100x100 polished button "Button" polished purple toggle "Toggle" polished blue red field bold "This is a field." polished effect [emboss tile] field bold "This is another field." polished effect [brighten 100] The image can be provided as a filename, URL, or image data. ===Backdrops A backdrop can be a color, an effect, an image, or a combination of the three. For example a backdrop color would be written as: backdrop navy title "Color Backdrop" gold To create a backdrop effect provide it on the line: backdrop effect [gradient 1x1 0.0.100 100.0.0] title "Gradient Backdrop" gold A backdrop image can be a file, URL, or image data: backdrop polished title "Image Backdrop" red The backdrop image can be colorized: size 400x500 backdrop polished blue title "Blue Image Backdrop" The image can include an effect: backdrop polished effect [fit gradcol 1x1 100.0.0 0.0.250] title "Gradient Image Backdrop" ===Backtile To make a backdrop use a tile effect there are two options: backdrop polished effect [tile] banner "This shows a backdrop with a tile effect" or backtile polished banner "This demonstrates backtile" Note the difference between: size 400x500 backdrop polished banner "Here one image is stretched to cover the canvas" and size 400x500 backtile polished banner "Here one image is repeated to cover the canvas" ===Effect Facets A range of effects are supported for faces. All of these effects are performed directly on the face when it is rendered. Here are examples of a few possible effects in top to bottom then left to right order: style polished-steel image 80x60 polished polished-steel effect [flip 1x1] polished-steel effect [rotate 90] polished-steel effect [reflect 1x1] polished-steel effect [crop 0x50 120x60 fit] polished-steel effect [grayscale] polished-steel effect [invert] polished-steel effect [difference 200.0.0] polished-steel effect [tint 80] return polished-steel effect [contrast 50] polished-steel effect [brighten 50] polished-steel effect [sharpen] polished-steel effect [blur] polished-steel effect [colorize 204.0.0] polished-steel effect [gradcol 1x1 150.0.0 0.0.150] polished-steel effect [gradmul 0x1 0.100.0] polished-steel effect [grayscale emboss] Effects can be used in combination to create other interesting results. However, keep in mind that the computations are performed in real time. If complex combinations are required, a temporary image should be created with the to-image function. ===Actions An action can be associated with almost any face. To do so, follow the face style with a block: button "Test" [alert "test"] The block is used as the body of a function that is passed the face and the current value (if the face has one). For example: toggle "Toggle" [alert form value] rotary "A" "B" "C" [alert form value] text "Click Here" [alert face/text] If a second block is provide, it is used for the alternate actions (right key): button "Click Here" [view/new layout [txt "action"]] [view/new layout [txt "alt-action"]] Use variables to modify the contents or state of other faces. For example, the slider will update the progress bar: slider 200x16 [p1/data: value show p1] p1: progress !More action on actions needed... ===Show After the state is changed for a user interface element, it must be re-drawn to be reflected on the user interface canvas. Accomplish this with the show message. backtile polished across toggle "Toggle State" [ cybernetics?/data: not cybernetics?/data show cybernetics?] return label "Are you interested in cybernetics?" cybernetics?: check One show command can be used for multiple user interface elements backtile polished orange across b1: check label "Red" return b2: check label "Green" return button 200 "Change State But No Refresh" [b1/data: not b1/data b2/data: not b2/data] return button "Show" [show [b1 b2]] ===Hide A user interface element can also be hidden. backtile polished orange across c1: check hide-button: button "Hide" [hide c1] return show-button: button "Show" [show [c1 d2]] The show-button action tries to show a user interface element 'd2' that does not exist. REBOL/View ignores these. ===Invisible Faces To make a button invisible when the view is opened, you can define an invisible button style This approach sets the show? value to false when the user interface element is initialized. across style invisible-button button with [append init [show?: false]] late-shower: invisible-button "I'm Here" return return button 200 "Show Invisible Button" [show late-shower] This works for the other visible user interface element. ===Focus A user interface element can programmatically be given the focus. across backtile polished button 200 "Set focus to Phone Field" [focus f2] return label "Name: " f1: field 100 return label "Phone: " f2: field 100 return button 200 "Remove focus from Phone Field" [unfocus f2] return button 200 "Hide the Phone Field" [hide f2] return ---Focus Defect !Note that the tab function shows a hidden field. I have assumed that this is a defect. If a field is hidden, the tab button should not make it visible. This has been previously sent to feedback. ===Radio Buttons A radio button is used to make a choice between mutually exclusive values. Your preferred programming language is REBOL or C++ or PL/1 or APL but it is only one of those. across backtile polished radio of 'programming-language pad 0x-4 label "REBOL" return radio of 'programming-language pad 0x-4 label "C++" return radio of 'programming-language pad 0x-4 label "PL/1" return radio of 'programming-language pad 0x-4 label "APL" return To mix two groups of radio buttons on one screen, associate them with their groups using the "of 'word". In the above, the grouping is 'programming-language. across backtile polished radio of 'programming-language pad 0x-4 label "Language: REBOL" return radio of 'programming-language pad 0x-4 label "Language: C++" return radio of 'editor pad 0x-4 label "Editor: TextPad" return radio of 'editor pad 0x-4 label "Editor: Notepad" return The padding in the above is needed to keep the label aligned with the radio button. across backtile polished orange radio of 'programming-language pad 0x-4 label "REBOL" return radio of 'programming-language label "APL" return ===Radio Button Settings A radio button is not very useful unless you can find out what its setting is and change that setting under program control. across backtile polished orange rebol-radio: radio of 'programming-language [programming-language: 'rebol] pad 0x-4 label "REBOL" return apl-radio: radio of 'programming-language [programming-language: 'apl] label "APL" return button 200 "Toggle radio button" [ apl-radio/data: not rebol-radio/data: not rebol-radio/data show [rebol-radio apl-radio] ] ===Check Box ---Purpose A check box is used to allow user interface choices where the choices are not mutually exclusive. across backtile polished orange c1: check label "Likes animals" return c2: check label "Like Monkees" return c3: check label "Like The Animals" ---State A check box is not much good if you can't get and set its state (on or off). across backtile polished orange c1: check label "Likes animals" return c2: check label "Like Monkees" return button "Set State" [ c1/data: true show c1 c2/data: false show c2 ] ===Sensor ---Purpose A sensor is an invisible user interface element. Using a sensor only makes sense in a few instances. If you want a keycode action where there is no visible user interface element to link the action to then a sensor can be used. This sensor code adds an Escape or Back or Enter action that will close the window. sensor 1x1 keycode [#"^M" #" " #"^(back)" #"^(ESC)"] [unview] Or if you want to make portions of an image 'hot' instead of putting buttons on top of the image, then a sensor will achieve this. across backtile polished orange txt "Click on the upper left section of the gray image to invoke the sensor action" return animage: image 100x100 polished ; here the image is just the polished area at animage/offset sensor 50x50 [alert "You pushed over the sensor"] ===Displaying Script Values If the script has a standard format headings, including custom ones, these can be used in the application by picking them from the system/script/header. backtile polished across banner "About" return text font-size 16 rejoin ["Title: " form system/script/header/title] return text font-size 16 rejoin ["Originator: " form system/script/header/author] return text font-size 16 rejoin ["Modifier: " form system/script/header/modifier] return text font-size 16 rejoin ["Version: " form system/script/header/version] return text font-size 16 rejoin ["Updated: " form system/script/header/date] return button "OK" [unview] ===Toggle A toggle button represents boolean state - either on or off. The button stays down until toggled again. Colors and text can be paired for "on" and "off" state. toggle "Up" "Down" red blue To set the state via program control, use: across backtile polished return t1: toggle "Up" "Down" red blue return button polished 204.0.0 100 "Toggle State" [ t1/state: not t1/state show t1 ] ===Rotary Buttons Rotary buttons are a different sort of user interface device. They can cause some challenges because the state is what's showing so you have to blindly "toggle" to get to a state that you want. But for quick and easy uses where the user is familiar with the options, they can be handy. If you plan to use them for a long list of items such as shown below, they might give you some usability concerns. ---Example across backtile polished rotary data ["First" "Second" "Third"] ---Setting State across backtile polished return r1: rotary data (my-options: ["First" "Second" "Third"]) return button 200 "Change Rotary State" [ r1/data: next r1/data if tail? r1/data [r1/data: head r1/data] show r1 ] ---Example - Usability For Unfamiliar List Contents The rotary button demonstrated here contains some information unfamiliar to most (Saturn's satellites). Use it to to set the state so that "Calypso" is set. Doable but without knowing the order each re-paint has to be checked to ensure that it is not "Calypso" before clicking again. If you do click past the choice that you want, there is no back function so you have to cycle through again. return rotary data [ "Pan" "Atlas" "Prometheus" "Pandora" "Epimetheus" "Janus" "Mimas" "Enceladus" "Tethys" "Telesto" "Calypso" "Dione" "Helene" "Rhea" "Titan" "Hyperion" "Iapetus" "Phoebe" ] ===Arrows REBOL/View supports arrows as simple user interface elements. Actions can be associated with them. ---Arrowheads And Actions By default, the arrow is 20x20 across size 200x100 backtile polished at 50x50 arrow left [alert "You pressed the left arrow"] [alert "You pushed the alternate button on the left arrow"] at 70x30 arrow up at 90x50 arrow right [alert "You pressed the right arrow"] at 70x70 arrow down ---Very Sharp Arrows And with a little work the arrows and boxes can be merged to look sharper. Here is a "sharp at both ends" arrow from the block diagram script by Carl: origin 0 backcolor white at 0x0 box 40x40 white effect [arrow rotate 270] at 110x0 box 40x40 white effect [arrow rotate 90] at 24x10 box black 100x20 ---Arrow Blend So that shows you how to make an arrow blend into your background size 100x100 across backdrop gray at 50x50 box 40x40 gray effect [arrow rotate 90] at 40x67 box 25x5 black ===LED LEDs would be used to display state (on or off). Clicking the LED toggles its state and changes its color. LEDs do not support alternate mouse button actions. across banner "Light Emitting Diode" return l1: led 10x10 [alert "LED left mouse action"] label "Alert status" l2: led 10x10 [alert "LED left mouse action"] label "Network status" return button "Change state" [ l1/data: not l1/data l2/data: not l2/data show [l1 l2] ] ===Box ---Boxing Draw boxes of any heigth and width with the box style box "Large Box" 200x400 polished orange ---Boxes As Lines If you make the box narrow enough or short enough it is a line (or a dot). across size 300x300 backtile polished at 50x0 box 3x100 gold at 0x50 b1: box 100x3 gold at 10x10 box 5x5 red ---Boxes Can Grow across size 300x300 backtile polished at 150x0 b1: box 100x3 gold return pad 0x100 button "Grow Down" [ for i 3 300 1 [ b1/size/y: 1 + b1/size/y wait 00:00:00.01 show b1 ] ] return pad 0x100 button "Back Up" [ for i 300 3 -1 [ b1/size/y: b1/size/y - 1 wait 00:00:00.01 show b1 ] ] You might even find a use for it. ---Grid Effect Not sure of the use for this yet but here is what you can do: return box "Grid Lock" with [effect: [grid 20x20 8x8 4x3]] white 300x200 return box "Grid Lock" with [effect: [grid 20x20 5x5 3x3]] white - 80 300x200 ===Frame Earlier versions of REBOL VID supported frames in layouts such as view layout [frame "This is the Bay" %bay.jpg] These are no longer valid. But frames can be put around some user interface devices: image 100x100 polished frame red ===List A list is an iterated sub layout and takes a layout block that uses the Visual Interface Dialect. The styles in the layout will be repeated until there is no more room to fit them within the list dimensions. ---Why A face can be iterated to create a number of virtual faces. For instance, when displaying a list of ten buttons, each of the buttons does not need to be created as a separate object. If the buttons only differ by a few facets (such as position, text, and action taken on selection), a model face can be created and iterated for its other position. This is useful when creating scrolling lists of files and other data sets that share the same appearance. ---Supply Supply provides the data to the list for an iterated face. do [cnt: 0 list-collection: [aqua sky water] ] backtile polished orange across list-displayed: list 100x72 [ origin 0 space 0x0 across color-field: txt bold 80x24 ] supply [ if none? one-color: pick list-collection count [exit] face/text: do pick [one-color] index ] return txt gold 180 "OK ... but not too useful" ---Supply Columns Maybe adding some more columns would be better. Here I'll add a column of buttons that display the color name and a column of text strings in italic. do [ cnt: 0 list-collection: [aqua sky water gold silver coffee] ] backtile polished orange across list-displayed: list 300x200 [ origin 0 space 0x0 across color-field: txt bold 80x24 color-button: button 80x24 pad 5x1 txt 100 italic ] supply [ if none? one-color: pick list-collection count [exit] face/text: do pick [ [one-color] [to-string one-color] [rejoin [" " to-string one-color]] ] index ] return txt gold 300 {A bit more interesting but the last row repeats to fill the list size. Some of the other VID components will automatically stretch to fit the size needed (such as this txt field) but the list does not behave that way. You have to make the list size fit its data or make it smaller and add a vertical scroll capability. That is shown a little later on.} ===List With Supplied Data This example is to show adding action to the list and adds a horizontal line between the rows. do [ cnt: 0 list-collection: [aqua sky water gold silver coffee] ] backtile polished orange across list-displayed: list water edge [size: 6x6 color: silver] 350x96 [ origin 0 space 0x0 across color-field: txt 60 [alert rejoin ["You pressed the " face/text " text field"]] pad 45x0 color-button: button 80 [alert rejoin ["You pressed the " face/text " button"]] pad 5x0 txt 120 italic return box 350x1 white ; this causes a horizontal line to appear between each row ] supply [ if none? one-color: pick list-collection count [exit] face/text: do pick [ [one-color] [to-string one-color] [rejoin [" " to-string one-color]] ] index ] ===Supply List With Scroll This example shows a supplied list with a scroll capability. More colors are added to demonstrate scrolling. Note that this is a verbose list of code where I added comments for my understanding of how the scroll was linked to the list. The same effect can be accomplished with fewer lines of code. do [ ; first this do block creates the data definitions needed. slider-position-clicked: 0 count: 0 x: 450 y: 300 row-y: 16 ; the row height includes the data plus any separator lines list-size: to-pair reduce [x y] ; this is the size of the display list separator-size: to-pair reduce [x 1] slider-size: to-pair reduce [24 y ] list-collection: [ aqua bar-color base-color beige black blue brick brown button-color coal coffee crimson cyan forest gold gray green ivory khaki leaf linen magenta main-color maroon mint navy oldrab olive orange over-color papaya pewter pink purple rebolor red sienna silver sky snow tan teal violet water wheat white yellow ] supply-style: stylize [ button-fixed: button left coal to-pair reduce [80 row-y] ; these keep the row elements the same height text-fixed: txt to-pair reduce [160 row-y] ] data-size: length? list-collection ] backtile polished orange ; this section layouts out the list across list-position: at ; the position is captured here in order to later put the slider beside it list-displayed: list linen edge [size: 6x6 color: tan] list-size [ origin 0 space 0x0 across styles supply-style text-fixed [alert rejoin ["You pressed the " face/text " text field"]] button-fixed [alert rejoin ["You pressed the " face/text " button"]] pad 5x0 text-fixed 80 italic [alert rejoin ["You pressed the italic " face/text " text field"]] return box separator-size gray ; this causes a horizontal line to appear between each row ] supply [ count: count + slider-position-clicked if none? one-color: pick list-collection count [exit] face/text: either count > (1 + data-size) [""] [ do pick [ [one-color] ; this is supplied to the first txt field (text-fixed) [to-string one-color] ; this is supplied to the button (button-fixed) [rejoin [" " to-string one-color " "]] ; this value is supplied to the last text-fixed field ] index ] ] ; now add a slider to the side of the list at list-position + (list-size * 1x0) ; this finds the top right border of the list widget vertical-slider: slider slider-size to-integer y / row-y [ slider-position-clicked: vertical-slider/data ; the slider has to be bound to the size of the list * ((1 + data-size) - ((y / (1 + row-y)))) ; including the row height if slider-position-clicked <> count [ count: slider-position-clicked show list-displayed ] ] ===Slider A slider is interactive user interface element. The data of a slider varies from 0 to 1. backtile polished orange across slider-1: slider 200x40 return button 200 "Move first slider to 50%" [ slider-1/data: .5 show slider-1 ] return txt 200 "The second slider in this example is initialized to the 80% mark." return slider 200x40 with [append init [data: .8]] ===Progress Indicator The progress-1 face in this example is a progress indicator. Because it is only displaying information, it is non-interactive i.e. you can not change its value by dragging its edges. The alternate button is not supported on a progress indicator. backtile polished orange across slider 200x40 [ progress-1/data: value field-1/text: join (to-integer (100 * value)) " %" show [progress-1 field-1] ] return progress-1: progress return field-1: field ===Panels Panels are used to create sub-panes that can be more easily managed by grouping the user interface devices on a panel. The first example below shows how to use panels for layout alignment. By creating a panel definition, all of the components defined within it are aligned relative to its origin. across backtile polished brick tabs 50 return panel-1: panel 250x120 [ backtile polished across return button water 200 "Button A" return button aqua 200 "Button B" return button sky 200 "Button C" ] at panel-1/offset + panel-1/size panel 60x90 [ ; start at the bottom right corner of panel-1 backtile polished across return button tan 20 "1" return button coffee 20 "2" ] ---Multiple SubPanels example This example from the REBOL html documentation shows how to easily hide and show sections of a user interface by displaying them on the face area of a box. do [ ; define two panels panel1: layout [ origin 8x8 h2 "Panel 1" field "Field 1" field "Field 2" button "The Answer" [alert "I know nothing."] ] panel2: layout [ origin 8x8 h2 "Panel 2" across txt "X:" slider 150x16 return txt "Y:" slider 150x16 return check [panel2/color: maroon show panel2] txt "Don't click this" return check [panel2/color: silver show panel2] txt "Click this" return ] panel1/offset: 0x0 panel2/offset: 0x0 ] vh2 "Subpanel Examples" ; now demonstrate panel use guide pad 20 button "Panel 1" [panels/pane: panel1 show panels] button "Panel 2" [panels/pane: panel2 show panels] button "Quit" [unview] return box 2x140 maroon return panels: box 220x140 do [panels/pane: panel1] ===Simple Default Style Override The style's default look can be overriden easily with one line of code. For example, to make the default button size 200x200 with a water color, use style button button 200x200 water button "Big Blue Button" [unview] To make the toggle some different default colors: style toggle toggle crimson sky toggle "Up" "Down" Note that these stay in effect until they are overridden so if you use the default values, exercise some care unless you meant to do that. ===Image Maker An option used by Carl in some of his programs is to let View create specific icons so that you have portability and more control of look of the image then if you referenced an external file such as gif that was a bullet display. Here's how to do that: do [ make-image: func [xy wh eff] [ eff: layout [ size 20x20 at xy box wh effect eff ] eff/color: rebolor to-image eff ] dot: make-image 6x5 9x9 [gradient 1x1 255.0.0 0.0.0 oval key 0.0.0] dot-big: make-image 8x7 12x12 [gradient 1x1 255.0.0 0.0.0 oval key 0.0.0] arr: make-image 3x3 14x14 [arrow 0.0.127 rotate 90] ard: make-image 3x3 14x14 [arrow 0.0.127 rotate 180] ] ; end of "do" - it is needed here because easyvid approach is expecting vid dialect commands banner "Presentation Points" size 400x300 across style label label gold ; make a label's text be a different color than the default return image dot label "This is bullet point number 1" return image dot label "This is bullet point number 2" return image arr label "This is arrow point number 1" return image ard label "This is an arrow making a different point" return image dot-big pad 0x4 area 300x80 wrap "And because these arrows and dots are images, action can be added to them to make them 'hot' with mouse actions including 'over'." ===Needs Some Work !More to come. These still need to be covered in this tutorial: text-list data [ icon ] ===Digital Clock origin 0 banner "00:00:00" rate 1 effect [gradient 0x1 0.0.150 0.0.50] feel [engage: func [face act evt] [face/text: now/time show face]] ===REBOL Logo image %rebo-logo.gif [unview] ===Paint Drops REBOL one liner by Vincent Ecuyer b: box rate 9 effect[draw[pen(random snow)circle(random 99x99)2]blur]box 1x1 rate 9 effect[draw[(b/image: to-image b)]] ===eMailer One line emailer by Doc Kimbel Assumes you have set up your email in set-user e: field "Email" s: field "Subject" m: area "Body" btn "Send"[send/subject to-email e/text m/text s/text alert "ok"] ===Hello World text "Hello World!" button "Close" [unview] ===Three Buttons button "Yes" button "Maybe" button "No" ===View Web Text text 800x600 read http://www.rebol.com ===View Image image %palms.jpg ===View Image and File Name Here a do block is used to initialize the file variable within the layout code. do [file: %palms.jpg] image file text form file ===View Image behind File Name Here a do block is used to initialize the file variable within the layout code. do [file: %palms.jpg] image file form file ===Buttons From Images backdrop 40.70.140 stat: text bold "Click a Button" 100x20 240.140.40 center button "Bay Test" %bay.jpg 100x100 [ stat/text: "Upper" show stat ] button "Blue Test" %bay.jpg 100x100 10.30.180 [ stat/text: "Lower" show stat ] ===View List list blue 320x200 [across text white 200 text white 100] data [ ["John" 100] ["Joe" 200] ["Martin" 300] ] ===Movie Credits backdrop %bay.jpg effect [fit] text center bold 240x30 "REBOL, The Movie" yellow font [size: 16] credits: text { Edit This File To Add Your Own Credits It is very simple to do. Only takes a minute. Only REBOL Makes It Possible... } white bold center 240x180 rate 30 para [origin: 0x+100] feel [engage: func [f a e] [ if a = 'time [f/para/origin: f/para/origin - 0x1 show f] ] ] ===Fire Demo box 150x150 with [ edge: none img: image: make image! 150x150 rate: 20 text: "FIREBOLEK" font: make font [size: 24 color: 255.125.0] basic: [draw [image make pair! reduce [(random 3) - 2 -1] img]] effects: reduce [ append copy basic [blur luma -10] append copy basic [sharpen luma -10 blur] append copy basic [contrast 10 blur luma -5] ] effect: first effects feel: make feel [ engage: func [f a e][ switch a [ down [f/effects: next f/effects if tail? f/effects [f/effects: head f/effects] f/effect: first f/effects show f] time [show f repeat i f/size/x - 4 [poke f/image (f/size/x * f/size/y) - i - 2 (random 255.0.0 + random 0.127.0) * 3] f/img: to-image f] ] ] ] ] text 150 {classical fire demo for REBOL^/ press on fire to see other effects.^/ Written by ReBolek, 2001 in 15 mins.^/ We need new category on Assembly:^/ less-than-kb-demo ;-)} with [font: make font [size: 9]] ===Bezier Oldes Bezier Line Demo See script library for %bezier-curve.r Uses functions and data initialized at script startup The end points are draggable to change the curve!!!! Here a do block is used to allow executable lines for initialization purposes. do [ draw-beziere-curve: has [result pp x0 x1 x2 x3 y0 y1 y2 y3 cx bx ax cy by ay t tx ty s] [ result: make block! 120 pp: p0/size/x / 2 x0: p0/offset/x + pp y0: p0/offset/y + pp x1: p1/offset/x + pp y1: p1/offset/y + pp x2: p2/offset/x + pp y2: p2/offset/y + pp x3: p3/offset/x + pp y3: p3/offset/y + pp insert result compose [ pen 155.0.0 line (p0/offset + pp) (p1/offset + pp) line (p2/offset + pp) (p3/offset + pp) pen 255.255.255 line (p0/offset + pp) ] cx: 3 * (x1 - x0) bx: 3 * (x2 - x1) - cx ax: x3 - x0 - cx - bx cy: 3 * (y1 - y0) by: 3 * (y2 - y1) - cy ay: y3 - y0 - cy - by t: s: 0.01 ;this value sets quality of the curve while [t <= 1][ tx: to integer! ( (ax * (t * t * t)) + (bx * (t * t)) + (cx * t) + .5 ) + x0 ty: to integer! ( (ay * (t * t * t)) + (by * (t * t)) + (cy * t) + .5 ) + y0 t: t + s insert tail result to pair! reduce [tx ty] ] return result ] click?: false mouse-pos: 0x0 ] origin 0 bkg: box black 400x400 with [effect: reduce ['draw make block! 120]] style point box 10x10 with [ effect: [draw [pen 0.255.0 fill-pen 0.200.0 circle 4x4 4]] changes: [offset] feel: make feel [ engage: func [f a e][ if a = 'down [click?: on mouse-pos: e/offset] if a = 'up [click?: off] if find [over away] a [ if click? [ f/offset: f/offset + e/offset - mouse-pos bkg/effect/2: draw-beziere-curve show [bkg f] ] ] ] ] ] at 300x200 p0: point at 200x100 p1: point at 200x300 p2: point at 100x200 p3: point do [bkg/effect/2: draw-beziere-curve] ===Buttons Galore Buttons galore from the library script %buttons.r Here a do block is used to execute the initialization needed within the layout block. do [ group: ["rotary" "test" "button"] ] origin 20x10 backdrop effect [gradient 0x1 100.20.0] vh1 "52 Button Click-up - Each with a different click effect..." vtext bold "Here is a small sampling of the thousands of button effects you can create. (This is 78 lines of code.)" at 20x80 guide button "simple" button form now/date button "colored" 100.0.0 button "text colored" font [colors: [255.80.80 80.200.80]] button with [texts: ["up text" "down text"]] button "bi-colored" colors [0.150.100 150.20.20] button with [texts: ["up color" "down color"] colors: [0.150.100 150.20.20]] button "image" pic button "color image" pic 200.100.50 button "flip color" pic with [effects: [[fit colorize 50.50.200][fit colorize 200.50.50]]] button "blink" with [rate: 2 colors: [160.40.40 40.160.40]] return button "multiply" pic with [effects: [[fit][fit multiply 128.80.60]]] button "brighten" pic with [effects: [[fit][fit luma 80]]] button "contrast" pic with [effects: [[fit][fit contrast 80]]] button "horiz flip" pic with [effects: [[fit][fit flip 1x0]]] button "vert reflect" pic with [effects: [[fit][fit reflect 0x1]]] button "invert" pic with [effects: [[fit][fit invert]]] button "vert grad" with [effects: [[gradient 0x1 0.0.0 0.200.0] [gradient 0x1 0.200.0 0.0.0]]] button "horiz grad" with [effects: [[gradient 1x0 200.0.0 200.200.200][gradient 1x0 200.200.200 200.0.0]]] button "both grad" with [effects: [[gradient 1x0 140.0.0 40.40.200] [gradient 0x1 40.40.200 140.0.0]]] button "blink grad" with [rate: 4 effects: [[gradient 1x0 0.0.0 0.0.200] [gradient 1x0 0.0.200 0.0.0]]] button "blink flip" pic with [rate: 8 effects: [[fit][fit flip 0x1]]] return button "big dull button with several lines" 100x80 0.0.100 button "dual color" pic 50.50.100 100.50.50 100x80 with [edge: [color: 80.80.80]] button "big edge" pic 100x80 with [edge: [size: 5x5 color: 80.80.80] effects: [[fit colorize 50.100.50][fit]]] button "oval reflect" pic 50.100.50 100x80 with [effect: [fit reflect 1x0 oval]] return button "text on top" pic 100x80 with [font: [valign: 'top] effects: [[fit gradcol 1x1 200.0.0 0.0.200] [fit gradcol -1x-1 200.0.0 0.0.200]]] button "text on bottom" pic 100x80 50.50.100 with [font: [valign: 'bottom] effects: [[fit][fit invert]]] button "big text font" pic 100x80 with [font: [size: 24] effects: [[fit multiply 50.100.200][fit]]] button "cross flip" pic 50.100.50 100x80 with [effect: [fit flip 0x1 reflect 0x1 cross]] return toggle "toggle" toggle "toggle red" 100.0.0 toggle "toggle up" "toggle down" toggle "toggle colored" 0.150.100 150.20.20 toggle "up color" "down color" 0.150.100 150.20.20 toggle "toggle multiply" pic with [effects: [[fit][fit multiply 128.80.60]]] toggle "toggle contrast" pic with [effects: [[fit][fit contrast 80]]] toggle "toggle cross" pic with [effects: [[fit][fit cross]]] toggle "toggle v-grad" with [effects: [[gradient 0x1 0.0.0 0.200.0] [gradient 0x1 0.200.0 0.0.0]]] toggle "toggle h-grad" with [effects: [[gradient 1x0 200.0.0 200.200.200][gradient 1x0 200.200.200 200.0.0]]] toggle "toggle both" with [effects: [[gradient 1x0 140.0.0 40.40.200] [gradient 0x1 40.40.200 140.0.0]]] return rotary data group rotary data reduce [now/date now/time] rotary data group 100.0.0 0.100.0 0.0.100 rotary data group with [font: [colors: [255.80.80 80.200.80]]] rotary data group with [colors: [0.150.100 150.20.20]] rotary data group pic rotary data group pic 200.100.50 rotary data group pic with [effects: [[fit colorize 50.50.200][fit colorize 200.50.50]]] rotary data group with [effects: [[gradient 0x1 0.0.0 0.200.0] [gradient 0x1 0.200.0 0.0.0]]] rotary data group with [effects: [[gradient 1x0 200.0.0 200.200.200][gradient 1x0 200.200.200 200.0.0]]] rotary data group with [effects: [[gradient 1x0 140.0.0 40.40.200] [gradient 0x1 40.40.200 140.0.0]]] ===Paint Program This section is a clip of the layout portion of Frank Sievertsen's remarkable paint program. Open this example to enable a quick link to the real source: button "Browse Source" [browse http://www.reboltech.com/library/html/paint.html] button "Close" [unview] In the example below, a DO block is used to execute initialize code. do [ color: fill-color: start: draw-image: draw-pos: tmp: none type: 'box undos: [] redos: [] draw: func [offset /local tmp] [ compose [ pen (color/color) fill-pen (fill-color/color) (type) (start) (either type = 'circle [ tmp: offset - start to-integer square-root add tmp/x ** 2 tmp/y ** 2 ] [offset]) ] ] ] backdrop effect compose [gradient 1x1 (sky) (water)] across draw-image: image white 300x300 effect [draw []] feel [engage: func [face action event] [ if all [type start] [ if find [over away] action [ append clear draw-pos draw event/offset show face ] if action = 'up [ append/only undos draw-pos draw-pos: tail draw-pos start: none ] ] if all [type action = 'down] [ start: event/offset ] ]] do [draw-pos: draw-image/effect/draw] guide style text text [ tmp: first back find face/parent-face/pane face tmp/feel/engage tmp 'down none tmp/feel/engage tmp 'up none ] label "Tool:" return radio [type: 'line] text "Line" return radio [type: 'box] on text "Box" return radio [type: 'circle] text "Circle" return style color-box box 15x15 [ face/color: either face/color [request-color/color face/color] [request-color] ] ibevel color: color-box 0.0.0 text "Pen" return fill-color: color-box text "Fill-pen" return button "Undo" [if not empty? undos [ append/only redos copy last undos draw-pos: clear last undos remove back tail undos show draw-image ]] return button "Redo" [if not empty? redos [ append/only undos draw-pos draw-pos: insert draw-pos last redos remove back tail redos show draw-image ]] ===Font Lab Carl's Font lab Here a do block is used to initialize some values needed in the layout do [ change-styles: func [style start facet subfacet value /local v][ start: find style/pane start foreach f start [ f: in f facet if subfacet <> 'none [f: in get f subfacet] either block? value [ if not block? get f [set f either none? get f [copy []][reduce [get f]]] either v: find get f value [remove v][head insert get f value] ][set f value] ] show style ] chg: func ['facet 'subfacet value] [ change-styles external-view norm-start facet subfacet value ] shad: does [chg font shadow sdir * to-integer sl2/data * 16] sdir: 1x1 sz: 180x40 sx2: sz/x / 2 ] style tgl toggle 60 style lab vtext bold backcolor rebolor space 0x5 across p: choice 180 "Sans-Serif Style" "Serif Style" "Fixed Width Style" [chg font name pick reduce [font-sans-serif font-serif font-fixed] index? p/data] return tgl "Bold" [chg font style [bold]] tgl "Italic" italic [chg font style [italic]] tgl "Lined" underline [chg font style [underline]] return tgl "Left" of 'tg1 [chg font align 'left] tgl "Center" of 'tg1 [chg font align 'center] tgl "Right" of 'tg1 [chg font align 'right] return tgl "Top" of 'tg2 [chg font valign 'top] tgl "Middle" of 'tg2 [chg font valign 'middle] tgl "Bottom" of 'tg2 [chg font valign 'bottom] return lab "Size:" 60x20 font [] sl: slider 120x20 [chg font size max 8 to-integer sl/data * 40] with [append init [data: .5]] return lab "Space:" 60x20 font [] sl1: slider 120x20 [chg font space (1x0 * to-integer sl1/data * 20) - 5x0] return lab "Shadow:" 60x20 font [] sl2: slider 120x20 [shad] with [append init [data: .5]] return lab "Shad Dir:" 60x20 arrow left [sdir: sdir * 0x1 + -1x0 shad] pad 6 arrow right [sdir: sdir * 0x1 + 1x0 shad] pad 6 arrow up [sdir: sdir * 1x0 + 0x-1 shad] pad 6 arrow down [sdir: sdir * 1x0 + 0x1 shad] pad 6 return button sx2 "Text Color" [chg font color request-color] button sx2 "Area Color" [chg color none request-color] return button sx2 "Help" [alert "Click the controls on the left to change text on the right."] button sx2 "Close" #"^Q" [unview] below at p/offset + (p/size * 1x0) + 10x0 norm-start: Title "Title" sz h1 "Heading 1" sz h2 "Heading 2" sz h3 "Heading 3" sz h4 "Heading 4" sz h5 "Heading 5" sz at norm-start/offset + (norm-start/size * 1x0) + 10x0 banner "Banner" sz vh1 "Video Heading 1" sz vh2 "Video Heading 2" sz vh3 "Video Heading 3" sz vtext "Video Text" sz text "Document Text" sz ===Windows Clipboard ---Cut or Copy to Clipboard Normal Windows cut and copy commands are supported e.g. on a field, contents can be copied to the clipboard. Programmatic access is also supported for text contents. across label "Entry field: " return input-field: field 200 "Enter your text here" return button 200 "Copy Entry field data to clipboard" [write clipboard:// input-field/text] return button 200 "Show Clipboard Contents" [alert read clipboard://] ---Clearing The Clipboard across button 200 "Clear The Clipboard" [write clipboard:// ""] return button 200 "Show Clipboard Contents" [alert read clipboard://] ---Paste from Clipboard Normal Windows paste commands are supported e.g. on a field, contents can be pasted. Programmatic access is also supported for text contents. across button 200 "Show Clipboard Contents" [alert read clipboard://] ===Requesters REBOL View supports an assortment of requesters. The results of the request-* code are returned as its value e.g. chosen-date: request-date ---Request Yes | No | Cancel Provides the user the capability to pick from choices "Yes" | "No" | "Cancel" The result is "True" | "False" | none do [user-response: none] button "Simple Request" 200 [user-response: request "Do you want to abandon your input so far?"] button "View User Response" 200 [alert form user-response] ---Pick A Color do [chosen-color: gold] button "Pick Color" 200 [chosen-color: request-color] button "View Chosen Color" 200 [alert form chosen-color] ---Pick An Answer The request allows a descriptive value then 1, 2, or 3 options. button "Format" 100 [request ["Your message goes here. It will wrap if it is very very long." "Choice 1" "Choice 2" "Choice 3"]] button "Example 1" 100 [request ["Pick The Color of Your New Model T" "Black"]] button "Example 2" 100 [request ["Pick one country" "England" "France"]] button "Example 3" 100 [request ["Run Extract Script?" "Yes" "No" "Cancel"]] ---Pick A Date do [chosen-date: 01-Jun-1990] button "Pick Date" 200 [chosen-date: request-date] button "See Chosen Date" 200 [alert form chosen-date] ---Get A LogonID and Password do [credentials: none] button "Get Credentials" 200 [credentials: request-pass] button "View Credentials" 200 [ view/new layout [ size 200x200 backtile polished orange across banner "Credentials" return label "LogonID: " txt pick credentials 1 return label "Password: " txt pick credentials 2 ] ] ---Pick A File Format: REQUEST-FILE /title title-line button-text /file name /filter filt /keep do [filter-block: ["*.gif" "*.jpg" "*.png" "*.bmp"]] button "Pick Any File" 300 [request-file "Select"] button "Pick With A Title" 300 [request-file/title "Pick The Data File to Process" "OK"] button "Change the Action Button Name" 300 [request-file/title "Pick The Data File to Process" "OK"] button "Keep Results" 300 [request-file/title/keep "Previous Select On This Button Is Kept" "OK"] button "Filter Files" 300 [request-file/title/filter "Pick An Image File" "OK" filter-block] ---Request Text Input Format: REQUEST-TEXT /offset xy /title title-text /default str button "Request Text Input - all default parameters" 300 [request-text] button "Request Text Input - with offset to window" 300 [request-text/offset 40x40] button "Request Text Input - with title" 300 [request-text/title "Input your question"] button "Request Text Input - with default" 300 [request-text/default "Key your question here"] button "Request Text Input - with all parameters" 300 [request-text/offset/title/default 100x100 "Input your question" "Key your question here"] ---Request Download from Net Request a file download from the net. Show progress. Return none on error. Format: REQUEST-DOWNLOAD url /to local-file backtile polished orange button "Request File Download To local REBOL Cache" 300 [request-download http://www.rebol.com/index.html] button "Request File Download To This Directory" 300 [request-download/to http://www.rebol.com/index.htmlnone] button "Request File Download To Specific File" 300 [request-download/to http://www.rebol.com/index.html%/c/temp.html] ===Message Box button "Format" 100 [request ["Your message goes here. It will wrap if it is very very long and tedious." "Close"]] button "Example" 100 [request ["You done good!" "OK"]] ---Confirmation button "Exit" 100 [ request/confirm "Do you want to quit without saving?" [] ] ===Calling the Editor The REBOL editor is now callable with the editor function backtile polished button 300 "Create a test file and edit it" [ write %temp.txt "This is a test file" editor %temp.txt ] frame 204.0.0 ===Calling Windows With View/Pro the calling of executables is supported. Here are two simple examples that will work if you have View/Pro on a platform where a notepad and calc are avaiable. across backtile size 200x200 return button "Notepad" [call ["notepad.exe"]] return button "Calculator" [call ["calc.exe"]] ===Window Options Note that these are options which are ignored by the easyvid.r code that displays them in this tutorial. Copy the code out and run it standalone in REBOL/View. ---Block Options: No Border and No Title view/options layout [ size 200x200 banner "Window Options" button "Close" [unview] ] [ no-border no-title ] ---Word Option: No Title Note that the results of this are surprising if you run it from within a script that has a title option. It is displayed near location 0x0 of the resulting window instead of in the window frame that has been suppressed. view/options layout [ size 200x200 banner "Window Options" button "Close" [unview] ] 'no-title ===REBOL/View Notifiers REBOL/View supports simple notifiers to send messages to a user interface ---Alert button 220 polished "Send alert message" [ alert "This causes a dialogue box to popup" ] ---Flash Flash is provided to provide a message and keep on processing. across size 200x200 return button 150 "Create Flash Message" [flash "Testing"] return button 150 "Unview Flash" [unview] ---Inform inform layout [ backtile polished sky across text font-size 16 bold underline red "Action complete!" return button "OK" [unview]] ---Popup REBOL supports popups (see note below before running!) across size 200x200 button "Show Popup" [ show-popup popup-layout: layout [ across size 200x200 backtile polished banner "The Popup Worked" return button "Unview" [unview] ] ] return button "Hide Popup" [unview/only popup-layout] I have had some difficulties (process lockup) when using these popups so just use view layout [...] and skip the popup part. ===Diagram Example Carl has created some diagrams in REBOL using styles to make an architecture diagram. This is a slightly modified version. Here again a DO block precedes the layout code for non-layout initiatiation ... here the definition of a function. Why make a diagram this way? 1. One reason is that it can be interactive ... the sections are all "hot" with a few lines of code. Here they pop up REBOL Dialogs but they could do anything that can be coded even something as simple as launching a browser on a different URL for each diagram component. The "Compositor" box demonstrates this by launching your browser on the REBOL.com site. 2. Very small footprint size compared to other presentation source formats. do [ information: func [info [string!]][ request/ok reform [ info] ] ] style bx box 255.255.255 0.0.0 font-size 11 font [color: 0.0.0 shadow: 0x0] edge [size: 5x2] [request/ok reform ["No information on" face/text]] style bb box bold left top para [origin: 6x10] edge [size: 2x2] [request/ok reform ["No information on" face/text]] backcolor silver + 30 at 15x15 h1 486 left "Arch Structure" at 15x50 bb "Client" 506x436 160.80.80 [ information "Any client machine e.g. branch or Call Centre"] at 25x252 bb "Mid-Tier" 486x68 effect [gradient 1x1 169.91.155 80.45.75] at 25x152 bb "UI" 486x96 effect [gradient 1x1 38.156.82 19.78.41] at 25x324 bb "Servers" 486x151 effect [gradient 1x1 103.96.200 50.45.100] [ information "Mid-tiers servers with XYZ relational database server" ] at 130x216 bx "Compositor" 182x24 bold [browse http://www.rebol.com] at 130x60 bx "Browser" 120x24 [information "Branch standard browser"] at 130x188 bx "Sound" 182x24 bold [information "Sound services"] at 255x60 bx "Win32" 120x24 [information "Win32 App"] ===Column Images Creates a layout looking (a little) like columns. It uses a gradient effect going from darker to lighter do [ column: make image! layout [ backdrop effect [gradient 1x0 20.20.20 250.240.230 luma 60] ] column-size: 50x420 area-size: 400x420 ; height should be the same as column-size ] backtile polished tan across image column-size column pad -10x0 ; this brings the default VID spacing back area wrap area-size edge none ; take the edge off of area so that it more closely blends shadow 2x2 pad -10x0 image column-size column ; if you want a right column ===Tree View of Directory This is Didier's tree view %request-dir.r In this sample, you must be online because the code is accessed on the Rebol script server do [do http://www.rebol.org/library/scripts/request-dir.r request-dir ] Note that: * the script is read from the script library but runs locally * it is showing the files in your directories ===The emailer Function The function for emailing has appeared in Jan-2004 on the rebol list. It is a simple idea ... to create a standard emailer by invoking a function emailer. This window will show the source: text wrap 400x300 mold get 'emailer And it is simple to run: across size 200x200 return button 150 "Run emailer" [emailer] But on my machine there is again a problem - the emailer locks up REBOL/View. Recommendation: * if it works use it if you like * use Doc Kimbel's one liner (works for me). Assumes you have set up your email in set-user e: field "Email" s: field "Subject" m: area "Body" btn "Send"[send/subject to-email e/text m/text s/text alert "ok"] * better yet, make your own... if the code for the basic is 1 line, then a custom version is not far away. Here's an example that allows selection of your frequent contacts (entered in the names-addresses series) and keeps a journal of email that you have sent (using this code) in file email-journal.txt. Assumes you have setup your user profile correctly to allow sending of email. do [ names-addresses: [ "Contact 1" [contact1-:-no-such-address-:-com] "Contact 2" [contact2-:-no-such-address-:-com] "Contact 3" [contact3-:-no-such-address-:-com] ] names: copy [] foreach [name address] names-addresses [append names name] journal?: false ; set to true if want to journalize sent email ] e: rotary 200 data sort names s: field "Subject" m: area 500x400 wrap "Body" btn "Send"[ send/subject who-to: select names-addresses e/text m/text s/text alert join "Sent email to: " form who-to if journal? [ write/append %email-journal.txt rejoin [ "[ When-sent: " now/precise " To: " who-to " Subject: {" s/text "} Message: {" m/text "} ] " newline ] ] ] btn "Quit" [unview] It won't take much to change this from the rotary used to a text list allowing multiple selections. ===Some More email Earlier there have been a few examples of sending email. Here are a few more that often appear in the mailing list ---Simple Send This is not a runnable version because you don't need anything but REBOL/Core to run it. It has been wrapped in a DO block so it does not send errors to the console. ---Quick Send Short Message do [ send [address-:-isp-:-com] "My Message" ] ---Send Longer Message Now a more complex message where there is a body to the message: do [ send [address-:-isp-:-com] {Sample Message This is the body of the message } ] ---Send with One Attachment Here, so that the sample does not fail, test file(s) are created by the code before attempting the send. do [ test-file: %file-attachment.txt write test-file {Just some test data to create a file} send/attach [address-:-isp-:-com] {Sample Message This is the body of the message } test-file ] ---Send with Attachments And a message with multiple attachments. Here, so that the sample does not fail, test file(s) are created by the code before attempting the send. do [ files: [%file-attachment.txt %second-attachment.txt] foreach file files [write file {Just some test data to create a file}] send/attach [address-:-isp-:-com] {Sample Message This is the body of the message } files ] ---Send to Multiple Addresses Here, so that the sample does not fail, test file(s) are created by the code before attempting the send. do [ files: [%file-attachment.txt %second-attachment.txt] foreach file files [write file {Just some test data to create a file}] send/attach [[address-:-isp-:-com][asecondAddress-:-isp-:-com]] {Sample Message This is the body of the message } files ] ---Send/only Same send only just provide the SMTP server with one copy: Here, so that the sample does not fail, test file(s) are created by the code before attempting the send. do [ files: [%file-attachment.txt %second-attachment.txt] foreach file files [write file {Just some test data to create a file}] send/only/attach [[address-:-isp-:-com][asecondAddress-:-isp-:-com]] {Sample Message This is the body of the message } files ] ---Send With Header This example uses a Do block to wrap the code. If you execute the email should be sent. But it is unlikely to be delivered. The addresses for me and you should be changed in your use as well as the * Subject * Organization * Content do [ me: [myaddress-:-isp-:-com] you: [youraddress-:-isp-:-com] header-object: make system/standard/email [ From: me Reply-To: me Subject: "Some Stuff" Organization: "Cyberia" MIME-Version: 1.0 Content-Type: "text/plain" ] send/header you {Test Message This is the message body. } header-object ] ---Send with CC This adds a copy value in the header-object do [ me: [myaddress-:-isp-:-com] you: [youraddress-:-isp-:-com] header-object: make system/standard/email [ From: me Reply-To: me Subject: "Some Stuff" Organization: "Cyberia" MIME-Version: 1.0 Content-Type: "text/plain" cc: [another-address-:-isp-:-com] ] send/header you {Test Message This is the message body. } header-object ] ---Doctored Code Again Doc Kimbel's one liner that does not waste a character e: field "Email" s: field "Subject" m: area "Body" btn "Send"[send/subject to-email e/text m/text s/text alert "ok"] ===Sharp Styles I really like the style that Didier has put around his email previewer do [ ss-light: stylize [ text: text feel none vtext: vtext feel none col-hdg: text black 255.255.204 bold middle effect [] col-txt: text edge [size: 1x0 color: gray effect: 'bevel] ban: vh3 left to-pair reduce [ 50 logo.gif/size/y] edge [ color: 0.0.0 size: 0x1] feel none with [color: black] lab: label para [origin: 2x3 margin: 0x2] labe: lab edge [size: 1x1 color: water effect: 'ibevel] inf: info 100 font-color yellow bkg: backdrop water - 10.10.10 txt-big: vtext 300 font-size 18 font-color yellow center rti: vtext font-size 14 bold txt-ch: rti font-color white 170x22 para [ origin: 2x3] with [font: make font [ color: white] colors: [55.95.155 235.170.55]] btnb: btn 70.70.70 font-color white men: rti 264 edge [size: 1x1 color: water effect: 'bevel] para [origin: 20x2 margin: 1x4] with [color: water - 40.40.40 effect: first effects: [ [draw [pen white fill-pen white polygon 5x2 13x10 5x18]] [draw [pen white fill-pen white polygon 2x5 10x13 18x5]] ] feel: none] ;system/view/vid/vid-feel/hot] cbox: box 60x20 edge [size: 1x1 color: water effect: 'bevel] [ if temp: request-color/color first face/data [face/color: temp change face/data temp show face] ] with [append init [color: first data]] ] stylesheet: ss-heavy: stylize/styles [ col-hdg: col-hdg effect [gradcol 0x1 200.200.160 155.155.104] ban: ban effect [merge gradcol 150.180.200 0.0.0] with [color: none] bkg: backdrop effect [gradient 1x1 65.125.175 45.75.115 grid 2000x4 1999x4 70.130.190 blur] txt-big: vtext 300 font-size 18 font-color yellow center rti: vtext font-size 14 bold txt-ch: txt-ch effect [gradcol -1x1 105.105.105 151.151.151] men: men effect [gradcol -1x0 black water] ] ss-light ] styles stylesheet space 4x4 origin 4x4 across bkg pad 15 ban 235 :title para [origin: 32x0] pad -254 image 30x30 %palms.jpg effect [fit key 255.0.255] } code: text: layo: external-view: none sections: [] layouts: [] space: charset " ^-" chars: complement charset " ^-^/" rules: [title some parts] title: [text-line (title-line: text)] parts: [ newline | "===" section | "---" subsect | "!" note | example | paragraph ] text-line: [copy text to newline newline] indented: [some space thru newline] paragraph: [copy para some [chars thru newline] (emit txt para)] note: [copy para some [chars thru newline] (emit-note para)] example: [ copy code some [indented | some newline indented] (emit-code code) ] section: [ text-line ( append sections text append/only layouts layo: copy page-template emit h1 text ) newline ] subsect: [text-line (emit h2 text)] emit: func ['style data] [repend layo [style data]] emit-code: func [code] [ remove back tail code repend layo ['code 460x-1 trim/auto code 'show-example] ] emit-note: func [code] [ remove back tail code repend layo ['tnt 460x-1 code] ] show-example: [ if external-view [xy: external-view/offset unview/only external-view] xcode: load/all face/text if not block? xcode [xcode: reduce [xcode]] ;!!! fix load/all if here: select xcode 'layout [xcode: here] external-view: view/new/offset layout xcode xy ] page-template: [ size 500x480 origin 8x8 backdrop white - 80 style code tt snow navy bold as-is para [origin: margin: 12x8] style tnt txt maroon bold ] parse/all detab content rules show-page: func [i /local blk last-face][ i: max 1 min length? sections i append clear tl/picked pick sections i if blk: pick layouts this-page: i [ f-box/pane: layout/offset blk 0x0 last-face: last f-box/pane/pane ; bh slider f-box/pane/pane/1/size: f-box/pane/size: max 500x480 add 20x20 add last-face/offset last-face/size ; bh slider update-slider ; bh slider show f-box ] show tl ; changed to after slider update ; was not refreshing the index display ] update-slider: does [ sld/data: 0 either object? f-box/pane [ sld/redrag min 1.0 divide sld/size/2 f-box/pane/size/2 sld/action: func[face event] compose [ f-box/pane/offset/2: multiply face/data (subtract 480 f-box/pane/size/2) show f-box ] ][ sld/redrag 1.0 show sld sld/action: none ] show sld ] main: layout [ backtile polished across vh2 title-line return tl: text-list 160x480 bold black white data sections [ show-page index? find sections value ] h: at f-box: box 500x480 at h + 500x0 sld: slider 24x480 ; add brett's slider at h + 456x-24 across space 4 arrow left keycode [up left] [show-page this-page - 1] arrow right keycode [down right] [show-page this-page + 1] pad -150 txt white italic font-size 16 form system/script/header/date/date ] show-page 1 xy: main/offset + either system/view/screen-face/size/x > 900 [ main/size * 1x0 + 8x0][300x300] view main | |
[unknown: 5]: 18-Dec-2008 | let me put it another way Steeve, I will not be reading more than 16 bytes per request (because I don't need any more than that) and it isn't a 16 bytes segment that is next to another 16 byte segment really I'm moving back and forth all over the file to get 16 byte segments each time. | |
Group: Script Library ... REBOL.org: Script library and Mailing list archive [web-public] | ||
sqlab: 2-Feb-2011 | The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache server at www7.swcp.com | |
Group: View ... discuss view related issues [web-public] | ||
james_nak: 4-Mar-2005 | Hello, Long time no talk. Is there a way to tell the request-file to open up in a specific directory? | |
Pekr: 22-May-2006 | should request-date/date 25-Jun-2006 bring me to that day? It does so for the first time only, consecutive invocation fails ... submitting to rambo .. | |
Group: I'm new ... Ask any question, and a helpful person will try to answer. [web-public] | ||
Pekr: 14-Apr-2009 | to [ aaaa | bbbb] is long time parse enhancement request, which is not yet implemented, but is planned for 3.0. It would really make lifes of parse beginners much easier. Your parse rule simply means - try to find "point-to-point" or the end of the line. But - it looks for the point-to-point till it reaches end of the input string. | |
Pekr: 2-May-2009 | Such functionality is long time request to parse enhancement, and is planned to be implemented ... | |
Gregg: 11-May-2009 | REBOL [] do %include.r include %file-list.r flash-wnd: flash "Finding test files..." if file: request-file/only [ files: read first split-path file ] if none? file [halt] items: collect/only item [ foreach file files [item: reduce [file none]] ] unview/only flash-wnd ;------------------------------------------------------------------------------- ;-- Generic functions call*: func [cmd] [ either find first :call /show [call/show cmd] [call cmd] ] change-each: func [ [throw] "Change each value in the series by applying a function to it" 'word [word!] "Word or block of words to set each time (will be local)" series [series!] "The series to traverse" body [block!] "Block to evaluate. Return value to change current item to." /local do-body ][ do-body: func reduce [[throw] word] body forall series [change/only series do-body series/1] ; The newer FORALL doesn't return the series at the tail like the old one ; did, but it will return the result of the block, which is CHANGE's result, ; so we need to explicitly return the series here. series ] collect: func [ "Collects block evaluations." [throw] 'word block [block!] "Block to evaluate." /into dest [block!] "Where to append results" /only "Insert series results as series" /local fn code marker at-marker? marker* mark replace-marker rules ][ block: copy/deep block dest: any [dest make block! []] fn: func [val] compose [(pick [insert insert/only] not only) tail dest get/any 'val get/any 'val ] code: 'fn marker: to set-word! word at-marker?: does [mark/1 = marker] replace-marker: does [change/part mark code 1] marker*: [mark: set-word! (if at-marker? [replace-marker])] parse block rules: [any [marker* | into rules | skip]] do block head :dest ] edit-file: func [file] [ ;print mold file call* join "notepad.exe " to-local-file file ;join test-file-dir file ] flatten: func [block [any-block!]][ parse block [ any [block: any-block! (change/part block first block 1) :block | skip] ] head block ] logic-to-words: func [block] [ change-each val block [either logic? val [to word! form val] [:val]] ] standardize: func [ "Make sure a block contains standard key-value pairs, using a template block" block [block!] "Block to standardize" template [block!] "Key value template pairs" ][ foreach [key val] template [ if not found? find/skip block key 2 [ repend block [key val] ] ] ] tally: func [ "Counts values in the series; returns a block of [value count] sub-blocks." series [series!] /local result blk ][ result: make block! length? unique series foreach value unique series [repend result [value reduce [value 0]]] foreach value series [ blk: first next find/skip result value 2 blk/2: blk/2 + 1 ] extract next result 2 ] ;------------------------------------------------------------------------------- counts: none refresh: has [i] [ reset-counts i: 0 foreach item items [ i: i + 1 set-status reform ["Testing" mold item/1] item/2: random/only reduce [true false] show main-lst set-face f-prog i / length? items wait .25 ] update-counts set-status mold counts ] reset-counts: does [counts: copy [total 0 passed 0 failed 0]] set-status: func [value] [set-face status form value] update-counts: has [pass-fail] [ counts/total: length? items pass-fail: logic-to-words flatten tally collect res [foreach item items [res: item/2]] ;result (e.g.): [true 2012 false 232] standardize pass-fail [true 0 false 0] counts/passed: pass-fail/true counts/failed: pass-fail/false ] ;--------------------------------------------------------------- main-lst: sld: ; The list and slider faces c-1: ; A face we use for some sizing calculations none ml-cnt: ; Used to track the result list slider value. visible-rows: ; How many result items are visible at one time. 0 lay: layout [ origin 5x5 space 1x0 across style col-hdr text 100 center black mint - 20 text 600 navy bold { This is a sample using file-list and updating progress as files are processed. } return pad 0x10 col-hdr "Result" col-hdr 400 "File" col-hdr 100 return pad -2x0 ; The first block for a LIST specifies the sub-layout of a "row", ; which can be any valid layout, not just a simple "line" of data. ; The SUPPLY block for a list is the code that gets called to display ; data, in this case as the list is scrolled. Here COUNT tells us ; which ~visible~ row data is being requested for. We add that to the ; offset (ML-CNT) set as the slider is moved. INDEX tells us which ; ~face~ in the sub-layout the data is going to. ; COUNT is defined in the list style itself, as a local variable in ; the 'pane function. main-lst: list 607x300 [ across space 1x0 origin 0x0 style cell text 100x20 black mint + 25 center middle c-1: cell cell 400 left cell [edit-file item/1] ] supply [ count: count + ml-cnt item: pick items count face/text: either item [ switch index [ 1 [ face/color: switch item/2 reduce [none [gray] false [red] true [green]] item/2 ] 2 [mold item/1] 3 ["Edit"] ] ] [none] ] sld: scroller 16x298 [ ; use SLIDER for older versions of View if ml-cnt <> (val: to-integer value * subtract length? items visible-rows) [ ml-cnt: val show main-lst ] ] return pad 0x20 f-prog: progress 600x16 return status: text 500 return button 200 "Run" [refresh show lay] pad 200 button "Quit" #"^q" [quit] ] visible-rows: to integer! (main-lst/size/y / c-1/size/y) either visible-rows >= length? items [ sld/step: 0 sld/redrag 1 ][ sld/step: 1 / ((length? items) - visible-rows) sld/redrag (max 1 visible-rows) / length? items ] view lay | |
Group: Parse ... Discussion of PARSE dialect [web-public] | ||
Pekr: 6-Nov-2008 | hmm, continuous parse ... there was my request for it long time ago, and IIRC even Carl said, that it might be usefull. Imagine for e.g. encoders ... You read stream from file in chunks, and you evaluate. The problem is, when you need to backtrack, you would need to cache the stream. Dunno, if something like that is possible at all ... | |
Group: MySQL ... [web-public] | ||
rolf: 26-Jan-2005 | @Gabrielle: AFAIK the scroller events just fire the SQL requests when the scroller is moved. So the request can overlap in time. The simple trick above solved the problem. | |
Dockimbel: 24-Jun-2006 | When a new request is sent through a timeout-ed connection, my driver will close the port and try to reconnect to the server. It tries 3 time and if it fails, generates an error. | |
Group: Linux ... [web-public] group for linux REBOL users | ||
Evgeniy Philippov: 27-Jan-2012 | One of the details I left out in the above overview is how clients actually render under wayland. By removing the X server from the picture we also removed the mechanism by which X clients typically render. But there's another mechanism that we're already using with DRI2 under X: direct rendering. With direct rendering, the client and the server share a video memory buffer. The client links to a rendering library such as OpenGL that knows how to program the hardware and renders directly into the buffer. The compositor in turn can take the buffer and use it as a texture when it composites the desktop. After the initial setup, the client only needs to tell the compositor which buffer to use and when and where it has rendered new content into it. This leaves an application with two ways to update its window contents: 1. Render the new content into a new buffer and tell the compositor to use that instead of the old buffer. The application can allocate a new buffer every time it needs to update the window contents or it can keep two (or more) buffers around and cycle between them. The buffer management is entirely under application control. 2. Render the new content into the buffer that it previously told the compositor to to use. While it's possible to just render directly into the buffer shared with the compositor, this might race with the compositor. What can happen is that repainting the window contents could be interrupted by the compositor repainting the desktop. If the application gets interrupted just after clearing the window but before rendering the contents, the compositor will texture from a blank buffer. The result is that the application window will flicker between a blank window or half-rendered content. The traditional way to avoid this is to render the new content into a back buffer and then copy from there into the compositor surface. The back buffer can be allocated on the fly and just big enough to hold the new content, or the application can keep a buffer around. Again, this is under application control. In either case, the application must tell the compositor which area of the surface holds new contents. When the application renders directly the to shared buffer, the compositor needs to be noticed that there is new content. But also when exchanging buffers, the compositor doesn't assume anything changed, and needs a request from the application before it will repaint the desktop. The idea that even if an application passes a new buffer to the compositor, only a small part of the buffer may be different, like a blinking cursor or a spinner. | |
Group: Web ... Everything web development related [web-public] | ||
Chris: 16-Jan-2007 | Etags should work like this: client requests a resource, server returns resource and etag header. Client again requests resource, but this time sends if-none-match header with etag value and server can then decide whether to process the request or send 304 not changed. I haven't explored this much so don't know how well it's supported -- I'm not sure how appropriate the solution is, but would involve the least server activity. | |
CharlesS: 24-Jan-2007 | yes, I am sending it each time, but for some reason it seems to only like the first request, after that it expires , or something else is going wrong ... Id really like to see a client with transparent support for cookies | |
Group: Announce ... Announcements only - use Ann-reply to chat [web-public] | ||
Chris: 21-Apr-2007 | Introducing QuarterMaster: Yet Another Web Framework that I'm probably going to have to take time to document properly: http://www.ross-gill.com/QM/ In short, it is designed around the MVC pattern. It is open source (license tbd). Tries to be lightweight, but could use some work. Tries to be as thin a wrapper to Rebol (/Core, /Base, whatever) while providing key functions for creating web sites/applications. Includes a flat-file dbms out the box, which generally works. Currently coded to work with Apache (needs mod-rewrite and 'request-uri' env variable), but should eventually be httpd agnostic. Please try, please test. I will answer all and every question (within reason). All suggestions considered with an open mind... Group: !QM | |
Group: !RebGUI ... A lightweight alternative to VID [web-public] | ||
shadwolf: 9-Jun-2005 | request-date give you a hudge over see spinner date give you a close contrôle for short time periode since now/date | |
shadwolf: 9-Jun-2005 | for example Image I'm a commercial I need to set for tomorow a schedule with some client what would be grphically better for me ? click add button and then select the date user request date or Click Add button then use spinner to select the proper date and time and enter an entry to the topic field :) | |
shadwolf: 11-Jun-2005 | Perk the translucent window capability is anOS feature that I request since lot of time but the key point is that this function is only accessible for some OS and for Linux it's a enligntenement layer (doesn't work with other X11 based windows manager ) example eterm is translucent but works only with enligtenment windows manager (the ones that comes with gnome ) | |
Ashley: 4-Mar-2007 | build#60 committed to SVN. Added Henrik's button widget with 2 minor modifications: 1) Over color defaults to colors/over 2) All of init inlined into the effect facet The first change is self-explanatory, the second follows the principle that init should do as little as possible (facet code is evaluated once while init code is evaluated every time the widget is used). This change has one subtle side-effect, the "Refresh Display" button of %tour.r no longer works for all widgets (button in particular). This will be fixed in a future build. One thing to note about the new button widget is its default size: 15x6 instead of 15x5 units. This should not be a problem for most buttons, but may have spacing/alignment issues for inline buttons. Note that the button change necessitated a small change to request-date which is now working again. | |
Pekr: 18-Apr-2007 | as for request-progress - I propose the same usage as with Calendar! Not every time you want a dialog box, which is stupidly blocking your UI. | |
Ashley: 17-May-2007 | directory selector that can access directories across the network We're limited to what "read %/" can pick up. Real solution is to have a native request-dir func (and request-color, request-font). background colour to an info field ... how about making it the same color as tooltips? field ctx-rebgui/colors/tooltip-fill Any ideas ... looks like a RebGUI bug as I can reproduce it with: display "" [ box tip "Some text" button [alert "Text"] ] Hmm, also noticed that tooltip and tooltip-time are dynamically escaping to the global context. Will look at this later today. | |
Ashley: 31-Jul-2009 | changed from single color web like look to some W9x look, was there any reason? ... commercial reality ;) where would I have changed the font? ... ctx-rebgui/effects/font request-char somehow misbehaves here ... bug, noted fonts must be handled differently in w7s ... I don't have access to W7 at home, but will check this Monday at work where do I set my UI options? Design time with ctx-rebgui/effects, /colors /behaviors and /sizes Adding request-ui back so you can alter these values from a GUI is trivial ... what I've removed is the rebind logic that enabled you to dynamically change values (i.e. you would have to re-do %rebgui.r to see any UI changes take effect ... not very practical for an SDK app) they look like W9x ... the color scheme (with the colors/page change noted above) is taken straight from W7 don't like gradiented buttons/tab ... based on W7 and Mac I thought Ashley wanted to go more web way, not desktop app way ... I've actually gone for something halfway (simpler than OS, more complex than Web) is it using a smaller font? ... 12pt by default as always (maybe W7 renders it differently than XP?) everything seems much smaller ... bigger screen? ;) I would welcome tour.r would fit 1280x800 notebook ... RC1 is about getting the basic functionality right, %tour.r and %RebDOC.r will both be made to run 1024x768 used to fit ... they havn't been reworked yet Windows XP with 1366 x 768 ... ... will be fixed with above | |
Ashley: 9-Aug-2009 | Build 207 - Fixed slider bug (zero divide error when ratio = 1) - Added find-key-face to needed funcs when not using view.r - Added undisplay (does what unview/only does, but better) - request-error now accepts string - Removed gui-error (obsoleted by request-error) - Removed find-face func - Cosmetic changes to: - led - led-group - radio-group - chat - Removed tip & over? attributes - Made init, options & old-color attributes optional - Made action & feel objects optional - Replaced rebface, subface, gradface & btnface with baseface & gradface - Added over? function - icon changed to accept file name directly - Added action/on-time event (used in conjunction with rate - see anim) - Added table & text-list alternate row coloring | |
btiffin: 17-Sep-2009 | Ashley; RebDOC feature request. How hard would it be to add a Keywords tab to this uber handy app? (Second part of the request being a please please if it won't take too much of your time) | |
Group: Cookbook ... For http://www.rebol.net/cookbook/requests.html [web-public] | ||
Sunanda: 3-Jan-2006 | Tom started this group with a reference to http://www.rebol.net/cookbook/requests.html It's a set of outstanding requests for cookbook entries -- ie examples that people would like to see. As he says.some have been done independently of the request, and published on the REBOLn Altmes or the Mailing List. It'd be a great collective community New Year's resolution to clear some of the cookbook request by the end of the month (and that leaves plenty of time to enter the competition too) | |
Group: DevCon2005 ... DevCon 2005 [web-public] | ||
Gabriele: 21-Jul-2005 | btw, i will not send the payment request immediately. no need for that right now; (especially the banquet). but, please hurry if you want an hotel reservation! the sooner you register, the more time we have to arrange things and so on. | |
Group: SVG Renderer ... SVG rendering in Draw AGG [web-public] | ||
Steeve: 13-Oct-2009 | My, my, my... I think some features in SVG, are too much work to implement with Rebol. 1/ The "objectBoundingBox" units. Which means, coordinates and lengths are ratio or percentages. And they are converted to real units depending of the bounding box of the shape on which they apply. It's easy to calculate when the shapes are boxes or vectors. But when it comes with arcs or curves, it becomes a pain in the ass. It's not a real problem because Inkscape for example has an option (simplify shapes) to convert all the ratio units in real units (ie. pixel units). So, I don't see the interest to rewrite DRAW from scratch with Rebol. (because it's what it means, to be able to calculate all the bounding box) 2/ Outlines with gradients Those fullishs can specify a gradient for the pen attribute (which draw the outlines). Rebol can only have a gradient to fill a shape. It can be simulated by drawing the related shape 2 times. 1 time with the pen gradient. A second time with the fill-pen attribute (which can be a gradient too). But the second time the shape must be, at first, downsized of the line width. To do so, it means that we need to know the center of the Bounding box of the shape. So, same problem than 1/ 3/ The fill-pen attribute (gradient or color) never apply on the outline of the shape, event if the outline has no color but actually has a width. It allows SVG for example, to have transparent outlines. We can't do that with Rebol. Because the fill-pen attributes (or the gradient) fills all the shape at first. And then the outline is drawed over. If we don't provide a pen color, or we provide a transparent color, we see the fill-pen content instead, at the place of the outline. Perhaps, that can be modified in Draw. A nice request but not a so considerable feature to my mind. (And it can be impossible to implement this in Draw, if AGG doesn't support it at first). | |
Group: Rebol School ... Rebol School [web-public] | ||
Vladimir: 5-Nov-2008 | Here is log from rebol ftp upload: No. Time Source Destination Protocol Info 67 3.356898 192.168.2.108 194.9.94.127 TCP spiral-admin > ftp [SYN] Seq=0 Win=16384 Len=0 MSS=1460 79 3.982028 194.9.94.127 192.168.2.108 TCP ftp > spiral-admin [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1100 80 3.982082 192.168.2.108 194.9.94.127 TCP spiral-admin > ftp [ACK] Seq=1 Ack=1 Win=16500 Len=0 90 4.056926 194.9.94.127 192.168.2.108 FTP Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ---------- 92 4.057544 192.168.2.108 194.9.94.127 FTP Request: USER visaprom.com 102 4.129540 194.9.94.127 192.168.2.108 FTP Response: 331 User visaprom.com OK. Password required 103 4.129689 192.168.2.108 194.9.94.127 FTP Request: PASS Du4m1t0R 106 4.241608 194.9.94.127 192.168.2.108 FTP Response: 230-User visaprom.com has group access to: www 107 4.241781 192.168.2.108 194.9.94.127 FTP Request: SYST 118 4.305921 194.9.94.127 192.168.2.108 FTP Response: 215 UNIX Type: L8 119 4.306117 192.168.2.108 194.9.94.127 FTP Request: PWD 134 4.367656 194.9.94.127 192.168.2.108 FTP Response: 257 "/" is your current location 136 4.370939 192.168.2.108 194.9.94.127 FTP Request: PORT 192,168,2,108,13,111 143 4.435976 194.9.94.127 192.168.2.108 FTP Response: 200 PORT command successful 144 4.468135 192.168.2.108 194.9.94.127 FTP Request: CWD apl/ 194 5.499179 192.168.2.108 194.9.94.127 FTP [TCP Retransmission] Request: CWD apl/ 198 5.565745 194.9.94.127 192.168.2.108 FTP Response: 250 OK. Current directory is /apl 199 5.565955 192.168.2.108 194.9.94.127 FTP Request: TYPE I 275 7.640872 194.9.94.127 192.168.2.108 FTP Response: 200 TYPE is now 8-bit binary 276 7.641186 192.168.2.108 194.9.94.127 FTP Request: STOR ik104test.zip 290 7.903130 194.9.94.127 192.168.2.108 TCP ftp > spiral-admin [ACK] Seq=613 Ack=111 Win=16500 Len=0 1279 37.655879 192.168.2.108 194.9.94.127 TCP spiral-admin > ftp [FIN, ACK] Seq=111 Ack=613 Win=15888 Len=0 | |
Vladimir: 5-Nov-2008 | No. Time Source Destination Protocol Info 90 2.750586 192.168.2.108 194.9.94.127 FTP Request: TYPE I 97 2.823074 194.9.94.127 192.168.2.108 FTP Response: 200 TYPE is now 8-bit binary 98 2.828500 192.168.2.108 194.9.94.127 FTP Request: PASV 113 3.171841 192.168.2.108 194.9.94.127 FTP [TCP Retransmission] Request: PASV 114 3.244193 194.9.94.127 192.168.2.108 TCP [TCP Previous segment lost] ftp > mgemanagement [ACK] Seq=80 Ack=15 Win=16500 Len=0 131 3.889034 194.9.94.127 192.168.2.108 FTP [TCP Retransmission] Response: 227 Entering Passive Mode (194,9,94,127,250,69) 137 3.984887 192.168.2.108 194.9.94.127 FTP Request: STOR ik104test.zip 149 4.247163 194.9.94.127 192.168.2.108 TCP ftp > mgemanagement [ACK] Seq=80 Ack=35 Win=16500 Len=0 210 7.046287 194.9.94.127 192.168.2.108 FTP Response: 150 Accepted data connection 241 7.218716 192.168.2.108 194.9.94.127 TCP mgemanagement > ftp [ACK] Seq=35 Ack=110 Win=16269 Len=0 1613 17.145048 194.9.94.127 192.168.2.108 FTP Response: 226-File successfully transferred 1617 17.172970 192.168.2.108 194.9.94.127 FTP Request: SIZE ik104test.zip 1620 17.277591 194.9.94.127 192.168.2.108 FTP Response: 213 566605 1623 17.375906 192.168.2.108 194.9.94.127 FTP Request: TYPE A 1628 17.498619 194.9.94.127 192.168.2.108 FTP Response: 200 TYPE is now ASCII 1629 17.516657 192.168.2.108 194.9.94.127 FTP Request: PASV 1633 17.644044 194.9.94.127 192.168.2.108 FTP Response: 227 Entering Passive Mode (194,9,94,127,205,237) 1637 17.750889 192.168.2.108 194.9.94.127 FTP Request: LIST 1643 17.835367 194.9.94.127 192.168.2.108 FTP Response: 150 Accepted data connection 1644 17.863490 194.9.94.127 192.168.2.108 FTP Response: 226-Options: -a -l 1645 17.863548 192.168.2.108 194.9.94.127 TCP mgemanagement > ftp [ACK] Seq=75 Ack=364 Win=16015 Len=0 | |
Group: rebcode ... Rebcode discussion [web-public] | ||
Robert: 5-Nov-2005 | graph-layout: I won't have the time to get deeper into rebcode in the moment. So, here is a request, for something that gives a nice demo: I have the old graph-layout code, which uses the TouchGraph idea. Anyone interested to port it to rebcode and see howmany nodes we can handle? | |
Group: RT Q&A ... [RT Q&A] Questions and Answers to REBOL Technologies [web-public] | ||
BrianH: 12-Oct-2005 | (By request, relayed from rebcode group) Could you add an APPLY opcode to rebcode? apply: ["Apply function or path to arguments, save result" word! word! | path! block!] In rebcode: apply x f [arg1 arg2 ...] Is equivalent to this in REBOL: x: do f arg1 arg2 ... The advantage to doing function calls this way is that the arity of the opcode is fixed, even if the arity of the function called can't be known ahead of time. The value assigned to the function word could be either a function or a path, or for efficiency you could have a seperate opcode APPLYP for path values (I'd prefer just one opcode for generality but it's your call). | |
Group: Syncing ... Syncing technologies [web-public] | ||
Pekr: 4-Jan-2006 | I would like to have answered: 1) what technique to use for "timestamping" - do we continue with timestamps against one central time, or do we use hashes, or sequencing numbers, or mixture of mentioned techniqueues? We might look how others do it ... 2) better support for possible conflicts - imagine following scenario - you have some reblet, e.g. Contacts - one person starts editing it, then another person starts editing it too. First one syncs (saves changes), then second one does the same - changes of first ones are lost. How to aproach this - introduce some kind of resources locking? (not real locking, but we are message based, so could be queued) It could work as follows - person 1 wants to edit some record. Edit button posts request-for-lock. Lock is assigned. I other person tries to edit, it will not obtain lock. We could even introduce protocol level support, so that the person is informed, who has the lock, and how long. The trouble usually comes, when person goes off-line after the edit started - we need to remove dead-locks, so by default, I would lock for 20 minutes e.g. and the lock would have to be renewed, if person 1 wants to work longer with the given document ... another scenario is, when you actually start editing something which might require locking, but you start already being off-line. We could create lock-request, just not synced yet. Once you go on-line, you simply check seqno, if the lock is possible, and the given record not modified. But what if it was modified in the meantime? e.g. you might be working with stock system and someone else in the office sells few units, for which you may start writing offer for to another customer. Tough scenario - would like to know your opinion. Maybe some things simply need to be done on-line only? 3) I needed small file-sync scenario - could use IOS, but IOS can't sync and "forget". Simply idea is to have different kind of syncing techniques, so e.g. for file transfer you have dir to sync, if correctly synced, log it, forget it, delete it on client and or server (or not, it depends) as for IOS, local storage could be encrypted (or not), imported into RebDB (no single better solution so far introduced for rebol), sync-per-record or record-set could remain (record=document). RebDB on Serve would speed things up significantly too ... another possibility is to think outside the IOS terms, in more general way - simply thinking about world of objects, being in various states, with various life-time around internet and on-line or off-line devices. I think that maybe we could find some simpler solution than SyncML and the likes ... another point - such techniques should be transport independent, so I would not like to hear that it needs this or that ;-) So, anyone? | |
Group: !REBOL3-OLD1 ... [web-public] | ||
Geomol: 11-May-2006 | Ladislav, I don't have time to think it all to the end, but an advise: Keep it simple! I know, it's a very hard goal to reach, because we don't want to cut off possibilities. If it's possible for someone new to the language to use a feature like "function-local return" right away with expected result, and still the advanced programmer can use the feature in a way maybe not obvious at first, but that makes good sense, then it might be perfect. But don't make the advanced programmer happy, if it'll make things difficult for the newbie. recursive usage of the function that may request a return from different instances of the recursion sounds complicated at first. I think, you're right. We probably don't need such a feature. If the code (C source) become simpler by including the feature in recursion, then you might consider it though. | |
Louis: 23-Nov-2006 | rebol [ purpose: "Demonstrate how to use the findany function." note: {This is a function I would like included in Rebol3. One of you experts (I don't remember who) made this function for me, and I use it all the time. Do you see any ways it can be improved before I submit it? --- Louis } ] s: "findany will return true if it finds in this sentence any of the strings you enter in the request box." print [s newline] forever [ bs: copy parse (request-text/title "Enter the strings you want to find separated by a space.") none findany: func [ "Searches string x for any substring found in block ys." x [string!] "string" ys [block!] "block of substrings" /local pos ] [ foreach y ys [ if pos: find x y [return pos] ] ] either findany s bs [print true][print false] ] halt | |
Geomol: 13-Aug-2007 | - Carl managed two releases today, the last one added a request-file. - I've been working on some very thorough 64-bit decimal testing, and I found a couple of bugs. Better to find them now than after a public release. - I made a little program to help getting a view on the alpha situation. (tests, bugs, etc.) - I just had a talk with Carl, and he has some more to say about testing. He has a test script, that was used for VID2, that he wants to get running under R3. It should make it easier for all the testers to get more done faster. Testing this is big project, but there is progress all the time. Just 4 updates to the bug tracker yesterday, but more than 20 updates the day before. (Both new reports and solving/testing old bugs.) | |
Graham: 8-Aug-2009 | Request ... I would like now/time to always return the seconds. | |
BrianH: 2-Sep-2009 | Geomol, you can protect values already in R3 with PROTECT. Request granted ahead of time :) | |
btiffin: 17-Sep-2009 | Ashley; RebDOC feature request. How hard would it be to add a Keywords tab to this uber handy app? (Second part of the request being a please please if it won't take too much of your time) | |
shadwolf: 23-Sep-2009 | font rendering not taking advantage of AGG i'm completly agree since anti aliased doesn't works properly but this should be the time on that particular area to see the font rendering area under a new line of real time text processing and their is alot of amazing things to be done . in the end my request is simple i want my users to choose their own font they like on any ot the main OS brands and get the same result everywhere (even on online editing for example imagine the rebol.org integrating viva-rebol thrue rebol3 webrowser plugin to allow the script sumiters and owner to share editing of a script with bunch of select people. That's the qualité we should aim for.) | |
Pavel: 27-Nov-2009 | Gabriele, is it possible to dispatch multiple request to wiki TCP examples "pong" server listening on single port? It should be possible but for me second request is without response until the first still open. Your HTTP scheme is too much complicated to me as lecture reading :). I've tried to transform rebol.org webserver to R3, I've got response, but seems to me useles to serve one and one only connection at time when the port is asynchronous by nature. Any hint? | |
Group: Plugin-2 ... Browser Plugins [web-public] | ||
Cyphre: 4-May-2006 | Hello Josh! I have one request. Try to run this: under IE: http://www.rebol.cz/~cyphre/plugin-ie.html under Mozilla/FF etc.: http://www.rebol.cz/~cyphre/plugin-moz.html Drag the green box using mouse and try to move it quickly over the screen. You can see the time lag when the green box is updating the position. Now try this from normal Rebol/View console: do http://www.rebol.cz/~cyphre/plugin-moz-test.r You can see there is no lag and the green box is updated very quickly. Do yo have any idea what could cause this difference? my specualtions: 1. Are you always blitting the whole screen in the plugin versions? This could cause the slowdown as there should be updated only the part with green box on the screen. 2. Could be the slowdown cause by different(higher) amount of mouse events which are pumped from browser to the plugin? | |
Group: !Cheyenne ... Discussions about the Cheyenne Web Server [web-public] | ||
btiffin: 28-Apr-2007 | Cheering squad: Give us a "C", give us an "h" ... Go "Chris" On a more serious note. I've offered to help design/beta trial REBOL Want Ads. QuarterMaster seems like a candidate for this. There isn't any time pressure, as this will take a while, but what is your gut feel for Cheyenne support? From reading !Cheyenne you seem to have got a workable solution to get at the REQUEST-URI functionality? Or was that just me reading with rose-coloured glasses? Just FYI, the very first cut is going to be a blog.r test. But I think rebols would appreciate a little more. Thanks again by the way. | |
btiffin: 2-Jun-2007 | I've been playing. login.rsp <% user: "test" pass: "letmein" print [<html> <body> <pre>] help request help request/content help session help session/content print [</pre> </body> </html>] in-user: select request/content 'login in-pass: select request/content 'pass if all [user = in-user pass = in-pass][ session/content/login?: yes response/redirect "/testapp" ] %> REQUEST/CONTENT is a block of value: [] Everytime through...first time and after filling in the login form. | |
btiffin: 5-Sep-2007 | Yeah, QM conflicts with request and Vanilla conflicts with session (at the quick glance I've taken so far). These types of problems are pretty easy to fix given the motivation. REBOL is eminently readable; all it requires is a little motivation, time and judicious use of context or global find and replace. Collisions are always hit or miss, but the web related scripts usually collide just by nature of the higher level words being the perfect words for the concept at hand. People running Apache would never see these collisions. R3 holds a lot of promise in allowing us rebols the freedom for independent development that others can combine in fun and magical ways, worry free of this issue. Another year and this type of complaint should be a thing of distant memory. | |
Will: 12-Oct-2007 | RSP is the best way and the faster inexecution/response time (instead of Apache cgi, it doesn't need to load rebol and your init library at each request), to do dynamic stuff with Cheyenne. The API is very sleek and you can read about it in the downloadable documentation part of Cheyeene download. | |
Henrik: 15-Jul-2008 | DocKimbel, small request: Would it be possible to post the rsp guide, cheatsheet and docs as separate pages directly on the site? It's unpractical to have to download Cheyenne every time I switch machine, just to read the docs. Thanks. | |
Dockimbel: 31-Jan-2009 | New Cheyenne 0.9.19 beta version available for testing at : http://cheyenne-server.org/tmp/cheyenne-r0919.zip Tested only on Windows (my Linux image network has currently some issues). ChangeLog (diff-ed from last test version) : o RSP: an HTTP redirection in 'on-page-start won't evaluate the page script anymore. o CGI: mezz function READ-CGI now patched to be compatible with Cheyenne. That's the right way of reading POST data in REBOL CGI scripts. o RSP: fixed a bug in session/add when setting a block! value. o Task-handler: fixed a network error on first packet read (high load + fast hardware). o Task-handler: TCP keepalive mode activated (test workaround half-closed connections). o Task-master: o 'no-delay mode removed and replaced by 'keep-alive mode o now forks a new process as soon as one dies (not waiting for a new request) o fix a long standing bug in queued job module name mismatching (can happen under extreme load) o minor code cleanup o Uniserve: 'no-delay TCP network mode now switched off for all connections. Fixes a stability issue on Vista and probably on UNIX with very high load. o RSP: fix a bug in 'decode-multipart when there's no file received. o UniServe: new logger service. Now all info or error logs, and debug messages from CGI/RSP scripts are written in %trace.log. Additionnaly, you can now log messages using : - debug/print msg ; msg [string!] - debug/probe value ; any mold-able value - ?? word ; works like REBOL's '?? function - ? msg ; alias for debug/print o RSP: in debug mode, page generation time and SQL queries stats now added at bottom of pages. o RSP: error in events from %app-init.r now logged. o RSP: fix a rare RSP freezing issue when an error occurs in %RSP.r (for example, by a user script that breaks RSP sandbox). o RSP: sanboxing now protects from Exit/Return/Break calls made outside of a function context. o RSP: %misc/rsp-init.r file removed. o RSP/CGI: New config keyword added in global sections : 'worker-libs. It lists the librairies to load when a worker process is started. An optional 'on-quit section can be added to call cleanup code when the process quits. Examples : worker-libs [ %libs/mysql-protocols.r ... ] or worker-libs [ %libs/mysql-protocols.r ... on-quit [ %/libs/free-resources.r ] ] o Task-master: now you can reset all worker processes without stopping Cheyenne. This is usefull when you need to force non-RSP/CGI files reload (helper scripts, 3rd party librairies,...). Usage: Windows : tray icon -> Reset Workers UNIX : kill -s USR1 <pid> (<pid> is Cheyenne's main process ID) o Added a -w command line option to set the worker processes number. Usage: $ cheyenne -w <n> (n [integer!] : CGI/RSP process number) Use -w 0 to help debug CGI/RSP code by resetting worker processes after each request. (it's like calling "Reset workers" after each request). | |
Pekr: 18-Feb-2009 | What you describe would mean, than you can only do one CGI request at the time. Cheyenne will launch new CGI process at each request, hence your file operations could collide. I like SQLite very much, but they don't provide server level functionality. They are able to work at file-lock level, but dunno how solid it is ... | |
Janko: 18-Feb-2009 | I am not sure if cheyenne starts new process for each request , I suspect it uses async sockets and serves request at a time | |
Robert: 18-Feb-2009 | A DB handles this by having one file lock for the database file all the time, taking several request at the same time and doinga DB locking scheme on-top of the filesystem locking. | |
Dockimbel: 26-Feb-2009 | General answer: session data is exchanged by TCP for each RSP request, so the performance penality can be high for huge session data. That also means that your server won't be able to handle a lot of user session at the same time. | |
Dockimbel: 3-Mar-2009 | Let's clarify a few things : - Request/content is working OK in your example, there's no issue with that. - Using variables in PARSE rules without initializing them is a bad programming practice in my book. You *should* initialize them before using them (unless wrapped in a function which will do the work for you). If your parse rule fails, your code may error out (or you may get an unexpected value) when trying to print 'phone because it hasn't been initialized. - You seem to expect that RSP script will be evaluated in a fresh REBOL session each time. This is not the way RSP works. RSP uses persistent pre-forked processes for performances. If you expect a fresh REBOL session each time, then this is the CGI model which is an order of magnitude slower than RSP. - Even if RSP processes are persistent, they can be restarted or killed and you can't control which process will executed your script, so, just as a warning, you can't expect that a "global" variable will be still there for the next RSP script evaluation. If you need value persistency, use a session variable or write it to disk. | |
Dockimbel: 9-Aug-2009 | App-init.r : if you define a word! in a RSP script or in app-init event handlers, remember that it will only exists in the worker process context where it was called. It won't be defined in the other worker processes, so it will likely produce errors in your app. The only safe and multiprocess way is to use session object. This means that you currently can't have such thing as webapp global words (but you can at the session level). If REBOL had multithreading or, at least, an efficient IPC between REBOL processes (like shared memory), you would have such feature since the beginning. I was reluctant to extend my custom IPC to allow shared global values for RSP script because it would have an impact on performances, but maybe the added value worths it and the impact might not be so big (basically, a MOLD/LOAD + 2 TCP transfers of all shared data for each request). Perhaps, it's time to reconsider adding this feature? | |
Graham: 19-Aug-2009 | I think I may be able to get around this issue by tagging the request with a dummy time parameter. | |
Graham: 19-Aug-2009 | I think I'll just stick with putting a time stamp on each request to foil the cache | |
Graham: 19-Aug-2009 | That first redirection is an authentication request from google so it looks like you might not have been logged in to gmail at the time. I used your second suggestion and that seems to work fixing the caching issue. Good work! | |
Dockimbel: 20-Sep-2009 | Henrik, trying to answer your questions/issues : to serve multiple document roots on the same site without having separate domain names => Use sub-domains for such isolation. Everything that's under one domain can be accessed with /.. parent syntax. I think that you can hack it around with ALIAS, custom webapps on-page-start event handler, but there aren't clean solutions. Use sub-domains for such isolation. I think webapps require a bit more than static pages? => Just to make it clear, webapps are REBOL applications interfaced with external world using RSP scripts. Webapp are not meant to be container for *only* static pages (HTML/CSS/JS/images). attempt [load join request/config/root-dir %/app-init.r] ; TBD: report errors !!! [...] RSP: error in events from %app-init.r now logged. That's from the change log. That's not correct. => Yes it is. What's being logged so far is the errors caught at runtime in event functions declared in app-init. What need to be logged is the LOAD %app-init.r process (syntax errors at boot time). after a lot of experimentation, the latest encapped version was the only one that worked properly. Both encap and sources versions works well on Win/Mac/Unix. The issues you have are related to running a rebol app as daemon in console mode on a remote Unix server (without a UI desktop). Cheyenne can work in source mode on such server, but it's much easier and pratical to use it in binary form in such case (typical remote linux server case). | |
Will: 17-Oct-2009 | can be done easly, source is in your hand , do whatever you want with it, sorry I have no time this week and I see no use of timestamps in rsp usage, but if I get at least one more same request I will add it 8) | |
Dockimbel: 11-Nov-2009 | Comet requires a connection to stay open, so it looks like this will take a Uniserve process for each open connection. A Uniserve process (worker process) is not bound to a given client connection. Each worker accepts requests from ANY client connection, so it can handle hundreds of Comet-like connections with a few worker processes as long as each request doesn't take much time. For example, if each request takes 50ms, with 10 worker processes, you can handle 200 req/sec. | |
Terry: 12-Nov-2009 | This PHP code works fine.. <?php $password = "ClueCon"; $port = "8021"; $host = "127.0.0.1"; function event_socket_create($host, $port, $password) { $fp = fsockopen($host, $port, $errno, $errdesc) or die("Connection to $host failed"); socket_set_blocking($fp,false); if ($fp) { while (!feof($fp)) { $buffer = fgets($fp, 1024); usleep(100); //allow time for reponse if (trim($buffer) == "Content-Type: auth/request") { fputs($fp, "auth $password\n\n"); break; } } return $fp; } else { return false; } } function event_socket_request($fp, $cmd) { if ($fp) { fputs($fp, $cmd."\n\n"); usleep(100); //allow time for reponse $response = ""; $i = 0; $contentlength = 0; while (!feof($fp)) { $buffer = fgets($fp, 4096); if ($contentlength > 0) { $response .= $buffer."<br>"; } if ($contentlength == 0) { //if contentlenght is already don't process again if (strlen(trim($buffer)) > 0) { //run only if buffer has content $temparray = split(":", trim($buffer)); if ($temparray[0] == "Content-Length") { $contentlength = trim($temparray[1]); } } } usleep(100); //allow time for reponse //optional because of script timeout //don't let while loop become endless if ($i > 10000) { break; } if ($contentlength > 0) { //is contentlength set //stop reading if all content has been read. if (strlen($response) >= $contentlength) { break; } } $i++; } return $response; } else { echo "no handle"; } } $fp = event_socket_create($host, $port, $password); $cmd = "api show dialplan"; $response = event_socket_request($fp, $cmd); echo $response; fclose($fp); | |
Dockimbel: 7-Jan-2010 | That may be possible, but would be more complicated to support than web sockets as the server can't send data without getting a request. It will be hard to extend the web socket application framework without bloating it. Maybe a separated mod-comet would be a cleaner approach (but might duplicate a Iot of code in mod-socket). I will give it a look anyway, at least to estimate the time required to support it. | |
Terry: 21-Jan-2010 | I thought this scenario could be recreated using WAIT or a loop that takes some time. Here'a another scenario.. a very typical websocket use.. A request comes in from the client "IBM".. the ws-script then checks a remote server continuously pushing a new IBM stock quote update, second by second forever? | |
Kaj: 15-May-2010 | What do you mean by that? Cheyenne's UniServe task masters run in separate processes, so when one request takes time other task masters handle other requests, but within one request your code is executed serially, the way you program it. REBOL is single-tasking, after all | |
GrahamC: 29-Dec-2010 | This is my target script add-rapid3.rsp <% context [ d: now ; convert to gmt, and then to NZ time d: d - d/zone + localzone ?? d ; add-rapid3.rsp c: request/content ; c: [pain "3" ptgl "4" fn "2" rapid3 "5" fatigue "9" ros "6" ems "7" patient "7"] ?? c patient: select c 'patient pain: min 10 to-decimal select c 'pain fn: min 10 to-decimal select c 'fn ptgl: min 10 to-decimal select c 'ptgl ros: min 60 to-decimal select c 'ros fatigue: min 10 to-decimal select c 'fatigue ems: min 360 to-integer select c 'ems result: make object! [ patient: (patient) pain: (pain) fn: (fn) ptgl: (ptgl) ros: (ros) fatigue: (fatigue) ems: (ems) ] ?? result ] %> and the c is the dump from ?? | |
onetom: 19-Apr-2011 | i have an rsp like this: <% probe delta-time [ ... switch request/method [ get [...] post [...] ] ... ] %> if i make a GET, it's fast: $ time curl -s -D- http://localhost:8080/docs/rfq3 >/dev/null 0:00:00.003815 real 0m0.026s if i make a post, the rsp part is still fast, but the overall request is damn slow (even consequent requests too): $ time curl -d @xxx -D- http://localhost:8080/docs/rfq3 0:00:00.004595 real 0m2.034s | |
Group: DevCon2008 (post-chatter) ... DevCon2008 [web-public] | ||
Reichart: 19-Dec-2008 | My request for whom ever hosts the page is that they "think" they can keep the page in place for a long time in the future. My hope is to eventually get all these devcon pages over to one place for historical reasons. | |
Group: !REBOL3 GUI ... [web-public] | ||
Cyphre: 3-Mar-2010 | Maxim, no problem, I have not much time either now so feel free to clarify any time later. I was just wondering what you are looking for to satisfy your needs. And of course, you cannot request functionality of big complex 3D systems which are usually fat high-level layers over low level graphics libraries. You should think about the DRAW at the level of graphic library api, not application layer. So I more awaited comparison with OpenGL, DIrectX, Cairo, Qt , Java2d and so on. Anyway, I'm curious about your examples.... Also I don't understand what is so wrong on using dialect as an interface when Rebol should be the case where working with blocks, dialects etc. should be a plus. For example If you prefer interface based on function calls over dialect the I'd like to know what benefits you see in that approach etc. | |
Pekr: 29-Nov-2010 | Button can be focused. Small enhancement request - can we add enter reactor for the button? I would find it usefull being able to run the button action hitting enter :-) btw - panels-2 - can't focus any button after the script start. Only after I invoke first button press ... now R3 crashed big time :-) | |
Cyphre: 8-Jun-2011 | It's time to decide about propagation of events using actors in R3GUI so we would like to know your opinion on that. example: Let's have face A and face B which is inside face A. Currently, when you click mouse button on the face B and the face B has defined ON-CLICK actor the event is fired to that actor. If the face B have no ON-CLICK actor the event is not catched anywhere. We got a request to checnge this so there are few possible options we could use: 1. If face B doesn't have ON-CLICK actor defined then propagate the event up to its parent face (in our case face A) and up until any ON-CLICK is found. (If the face B have ON-CLICK defined then the actor is executed and propagation stops here.) In other words the event propagation stops in the closest found ON-CLICK actor during the 'bubbling' of the event upwards. 2. Propagate the event from face B thru its parent face (in our case face A) and up to the topmost(Window) face. The propagation/bubbling is done by default and can be stopped in any ON-CLICK actor on the way upwards by returning 'stop-event(or any other chosen) keyword. (this is simmilar to the model used in HTML) 3. (current behaviour) Don't propagate the event. Just execute the ON-CLICK actor in face B in case it is defined. Programmer have to manually add event propagation code to the actor if event bubbling is required. 4. Don't propagate the event by default. But introduce PROPAGATE/BUBBLE-ACTORS (or any other chosen word) option field that can be set for each face. The option could hold block of actor names that should propagate/bubble the events up. Please, keep in mind that chosen behaviour affects not only actors that handle user input but also actors like ON-INIT, ON-MAKE and any other possible actors in general. Please post either your favorite from the above options or even any other possible solution you think is better. Thanks for your help. | |
Pekr: 12-Oct-2011 | I understand that you are focusing resources as much as possible, otoh it is a bit dangerous aproach - R3 GUI saw rather intense concept changes during last year. Anyone eventually willing to give it a try once time permits will think twice, as recent public release could be pretty much outdated in few weeks, API wise, etc. There should imo be a way, that upon some request or bunch of requests, public release is done e.g once in few months? | |
Group: !REBOL3 ... [web-public] | ||
Maxim: 24-Aug-2010 | yes... most applications now are multi-threaded if only to make them smoother... the GUI in one thread, heavy lifting in another, for example. async, doesn't allow you to scale, only to time slice. you can still only compute on a single request at a time. if the request needs time to finish (rendering, for example), it effectively blocks all async and I/O handling. | |
Pavel: 3-Dec-2010 | An idea of NTP scheme, but servers comunicates only on 123 UDP port. overview of time services: Daytime: Ascii response, Graham and Ladislav has written a scheme/tool already port 13 Time: most simple possible server listening on port 37 answer 32bit unsigned number of second from 1-1-1900/0:00 (calculation of human readable date is not so trivial because of leaping seconds inserted to UTC with no rule at all, an Earth is dancing a Jive in fact) HTTP: use inserted Date-time from any header returned from server port 80 SNTP: more precise protocol (contains also fraction of second in reply) subprotocol of NTP on UDP port 37 NTP: most precise available to compare more time servers, and calculate with computed transport delay and phase shift from evaluated couple of handshaking packets. UDP port 37 The latter two use minimally 12 32bit binary packets for request and response, symmetric or asymetric cryptography possible (honestly I've no clue why this). |